 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier flight crew flying a B737 advanced cockpit near rdu reports accepting a heading from ATC that was meant for another aircraft.
| Attributes | |
| ACN | 483730 |
| Time | |
| Date | 200008 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : rdu.airport |
| State Reference | NC |
| Altitude | msl single value : 4000 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : rdu.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | arrival : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : flight engineer pilot : atp pilot : commercial |
| Experience | flight time last 90 days : 200 flight time total : 7980 flight time type : 4500 |
| ASRS Report | 483730 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : multi engine |
| Experience | flight time last 90 days : 250 flight time total : 14000 flight time type : 8000 |
| ASRS Report | 483729 |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other controllerb |
| Resolutory Action | controller : issued new clearance controller : provided flight assist flight crew : became reoriented none taken : detected after the fact |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Rdu approach control was working 2 frequencys -- 1 was 128.3, the one we were on. Our flight was being vectored for a visual approach to runway 5R at rdu. At 4000 ft, about 12 mi from the airport, approach gave us a 320 degree heading. After reading back 320 degree heading 4000 ft, the captain turned to heading 320 degrees for about 30 seconds. Later, ATC came back and said that heading was for someone else on the frequency and had us turn to a 180 degree heading. After reading that back, the captain turned to that heading. After just a couple more vectors, we landed visually at rdu. We believe the cause of this problem was ATC using 2 frequencys and not correcting us when we read back the heading of 320 degrees. End of statement.
Original NASA ASRS Text
Title: AN ACR FLC FLYING A B737 ADVANCED COCKPIT NEAR RDU RPTS ACCEPTING A HDG FROM ATC THAT WAS MEANT FOR ANOTHER ACFT.
Narrative: RDU APCH CTL WAS WORKING 2 FREQS -- 1 WAS 128.3, THE ONE WE WERE ON. OUR FLT WAS BEING VECTORED FOR A VISUAL APCH TO RWY 5R AT RDU. AT 4000 FT, ABOUT 12 MI FROM THE ARPT, APCH GAVE US A 320 DEG HDG. AFTER READING BACK 320 DEG HDG 4000 FT, THE CAPT TURNED TO HDG 320 DEGS FOR ABOUT 30 SECONDS. LATER, ATC CAME BACK AND SAID THAT HDG WAS FOR SOMEONE ELSE ON THE FREQ AND HAD US TURN TO A 180 DEG HDG. AFTER READING THAT BACK, THE CAPT TURNED TO THAT HDG. AFTER JUST A COUPLE MORE VECTORS, WE LANDED VISUALLY AT RDU. WE BELIEVE THE CAUSE OF THIS PROB WAS ATC USING 2 FREQS AND NOT CORRECTING US WHEN WE READ BACK THE HDG OF 320 DEGS. END OF STATEMENT.
Data retrieved from NASA's ASRS site as of July 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.