37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 952549 |
Time | |
Date | 201106 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | EWR.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Air/Ground Communication |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 57 Flight Crew Total 10100 Flight Crew Type 2910 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Event / Encounter Other / Unknown Ground Incursion Runway |
Narrative:
[We were] on ground frequency whilst taxiing on sierra northbound from the ramp. Ground has us switch to tower frequency approaching 29/11 and prior to crossing 29 was given 'cleared to cross 29 right on zulu; hold short 22R'. From this runway 22R on Z hold short position; tower cleared us 'left turn onto Z6 position and hold 22R' which created some confusion; as we didn't see this taxi designator on the airport page. We presumed it was the north arc to give full runway 22R and more importantly remain clear of runway 29.all [was] good so far.we were in position on 22R waiting for takeoff clearance and watching the arriving airplanes landing runway 29. [Two in a row made missed approaches and we were wondering] what contributing factors would cause two missed approaches!after the 2nd missed approach; I called on tower frequency that we were ready for an immediate takeoff. No reply. I presumed they had their hands full with the arrivals and missed approaches. Another arrival goes missed approach and I call tower again letting them know we can take an immediate. The captain and I are trying to figure out what is happening. It's certainly abnormal. Then the captain checked the #1 radio and finds it was tuned to departure frequency.while holding short of 22R at zulu; I had typed the departure frequency into the scratch pad. I usually leave this here in the scratch pad for the frequency change for departure. It seems like simplest exchange. How did it get into #1 radio? Certainly it must have occurred after tower gave us clearance into position and hold 22R.once en-route; we discussed the entire event and it began to make sense. Why the missed approaches on 29? Why no departures on 22R? Tower must have given us a takeoff clearance. As we didn't read it back; no one could land 29 nor depart 22R. Why didn't they call us on guard? I made two radio calls on; presumably; the wrong frequency. Why was there no communication from departure such as 'you guys are on the wrong frequency'.enroute; we were given a frequency change. The new frequency was entered and visually confirmed. Yet; when we made the radio call we were transmitting on the prior frequency. Could this have happened on the ground with the tower/departure frequency?
Original NASA ASRS Text
Title: An A300 flight crew inadvertently selected their departure control frequency when cleared to Line Up and Wait on Runway 22R at EWR. The resulting loss of communication resulted in three go arounds by aircraft approaching Runway 29.
Narrative: [We were] on Ground frequency whilst taxiing on Sierra northbound from the ramp. Ground has us switch to Tower frequency approaching 29/11 and prior to crossing 29 was given 'CLEARED TO CROSS 29 right on Zulu; hold short 22R'. From this Runway 22R on Z hold short position; Tower cleared us 'LEFT TURN ONTO Z6 POSITION AND HOLD 22R' which created some confusion; as we didn't see this taxi designator on the airport page. We presumed it was the north arc to give full Runway 22R and more importantly remain clear of Runway 29.All [was] good so far.We were in position on 22R waiting for takeoff clearance and watching the arriving airplanes landing Runway 29. [Two in a row made missed approaches and we were wondering] what contributing factors would cause TWO missed approaches!After the 2nd missed approach; I called on Tower frequency that we were ready for an immediate takeoff. No reply. I presumed they had their hands full with the arrivals and missed approaches. Another arrival goes missed approach and I CALL TOWER AGAIN letting them know we can take an immediate. The Captain and I are trying to figure out what is happening. It's certainly abnormal. Then the Captain checked the #1 radio and finds it was tuned to Departure frequency.While holding short of 22R at Zulu; I had typed the Departure frequency into the scratch pad. I usually leave this here in the scratch pad for the frequency change for departure. It seems like simplest exchange. How did it get into #1 radio? Certainly it must have occurred AFTER Tower gave us clearance into position and hold 22R.Once en-route; we discussed the entire event and it began to make sense. Why the missed approaches on 29? Why no departures on 22R? Tower must have given us a takeoff clearance. As we didn't read it back; no one could land 29 nor depart 22R. Why didn't they call us on Guard? I made two radio calls on; presumably; the wrong frequency. Why was there no communication from Departure such as 'you guys are on the wrong frequency'.Enroute; we were given a frequency change. The new frequency was entered and visually confirmed. Yet; when we made the radio call we were transmitting on the prior frequency. Could this have happened on the ground with the Tower/Departure frequency?
Data retrieved from NASA's ASRS site as of April 2012 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.