37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 830144 |
Time | |
Date | 200903 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 7000 Flight Crew Type 1000 |
Person 2 | |
Function | Enroute |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
We were placed in holding northeast of iah. Aus was our alternate. There were thunderstorms and we were placed in high altitude holding. We were concerned about fuel and the controller advised that the delay may be long enough to cause a divert to aus. If we waited; we were advised that we would be sent to the other side of the field for a different arrival -- not specified. Eventually; a cell neared our holding location. We asked to be moved and while waiting; the static on the radios made hearing center very difficult. Eventually; the captain and I both heard the controller phonetically spelling l-e-O-north-a. That is what the captain even wrote on his scratch paper. I was typing that in the FMS and hit direct. We were on about a 210 degree heading when another aircraft relayed a new frequency to us. At some point there we also heard to join an arrival off of leona. We checked on with the new controller who asked where we were going. We told him leona. He gave us a new heading to 270 degree and told us it was the LOA (leona) VOR and not the leona intersection. This all happened very quickly; but there were several factors that could have changed what happened. 1) if it were possible (and I don't know if it was) to give us the name of the expected arrival from the other side of the airport; we would have already seen that there was a VOR named leona. 2) the controller could have phonetically spelled the VOR identification and not the VOR name. This raises the question of why vors even need names at all in an FMS environment. 3) we could have had faster situational awareness of the fact that an intersection 400 miles away was probably a misunderstanding. Luckily it was solved easily and quickly as we regained communication ability.
Original NASA ASRS Text
Title: An air carrier aircraft's radios developed static that interfered with ATC instructions while holding near thunderstorms. The clearance understood by the crew was to LEONA intersection. ATC actually meant LOA VOR (LEONA) which the crew heard phonetically.
Narrative: We were placed in holding northeast of IAH. AUS was our alternate. There were thunderstorms and we were placed in high altitude holding. We were concerned about fuel and the Controller advised that the delay may be long enough to cause a divert to AUS. If we waited; we were advised that we would be sent to the other side of the field for a different arrival -- not specified. Eventually; a cell neared our holding location. We asked to be moved and while waiting; the static on the radios made hearing Center very difficult. Eventually; the Captain and I both heard the Controller phonetically spelling L-E-O-N-A. That is what the Captain even wrote on his scratch paper. I was typing that in the FMS and hit direct. We were on about a 210 degree heading when another aircraft relayed a new frequency to us. At some point there we also heard to join an arrival off of LEONA. We checked on with the new Controller who asked where we were going. We told him LEONA. He gave us a new heading to 270 degree and told us it was the LOA (LEONA) VOR and not the LEONA Intersection. This all happened very quickly; but there were several factors that could have changed what happened. 1) If it were possible (and I don't know if it was) to give us the name of the expected arrival from the other side of the airport; we would have already seen that there was a VOR named LEONA. 2) The Controller could have phonetically spelled the VOR ID and not the VOR name. This raises the question of why VORs even need names at all in an FMS environment. 3) We could have had faster situational awareness of the fact that an intersection 400 miles away was probably a misunderstanding. Luckily it was solved easily and quickly as we regained communication ability.
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.