<< >> NASA ASRS Report 108512, April 1989

During frequency change flight apparently selected wrong frequency and were unable to re-establish communication with previous controller.

Attributes
ACN	108512
Time
Date	198904
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : atr
State Reference	DE
Altitude	msl bound lower : 20000 msl bound upper : 20000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zdc artcc : zny
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 18000 flight time type : 5000
ASRS Report	108512
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 6000 flight time type : 1000
ASRS Report	108716
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	other

Narrative:

ZNY transferred our flight to another center frequency which was not the one we transferred to. The xmissions from ZNY were weak and reported weak by other aircraft. When we went over to the assigned frequency we were unable to contact him. We then called bwi approach control after contacting ZDC for the proper frequency. We should have been alerted by the reports of weak xmissions and our own observations that a communication snafu was possible. Supplemental information from acn 108716: we were never given, nor did we receive a handoff to the next sector. While we could still hear communication from the center they could not hear us. We continued on our routing while we tried several times to find a proper frequency.

Related reports:

• A flight crew lost communication and were able to re-establi...
• DC9 on vector for runway 3R dtw lost communication with appr...
• An air carrier medium large transport lost all communication...
• Air carrier medium large transport lost radio communication ...
• An MU2 pilot forgot his assigned frequency and contacted bfi...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: DURING FREQ CHANGE FLT APPARENTLY SELECTED WRONG FREQ AND WERE UNABLE TO RE-ESTABLISH COM WITH PREVIOUS CTLR.

Narrative: ZNY TRANSFERRED OUR FLT TO ANOTHER CENTER FREQ WHICH WAS NOT THE ONE WE TRANSFERRED TO. THE XMISSIONS FROM ZNY WERE WEAK AND RPTED WEAK BY OTHER ACFT. WHEN WE WENT OVER TO THE ASSIGNED FREQ WE WERE UNABLE TO CONTACT HIM. WE THEN CALLED BWI APCH CTL AFTER CONTACTING ZDC FOR THE PROPER FREQ. WE SHOULD HAVE BEEN ALERTED BY THE RPTS OF WEAK XMISSIONS AND OUR OWN OBSERVATIONS THAT A COM SNAFU WAS POSSIBLE. SUPPLEMENTAL INFO FROM ACN 108716: WE WERE NEVER GIVEN, NOR DID WE RECEIVE A HDOF TO THE NEXT SECTOR. WHILE WE COULD STILL HEAR COM FROM THE CENTER THEY COULD NOT HEAR US. WE CONTINUED ON OUR ROUTING WHILE WE TRIED SEVERAL TIMES TO FIND A PROPER FREQ.

Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.