 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier flight crew flying B737-300 from day read back the wrong heading instructions to ATC resulting in a track deviation.
| Attributes | |
| ACN | 433680 |
| Time | |
| Date | 199904 |
| Day | Sun |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : cvg.vortac |
| State Reference | OH |
| Altitude | msl bound lower : 8000 msl bound upper : 12000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | tracon : day.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other vortac |
| Flight Phase | climbout : initial |
| Route In Use | departure : on vectors departure sid : dayton 3 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : multi engine pilot : commercial pilot : atp pilot : instrument |
| Experience | flight time last 90 days : 240 flight time total : 12000 flight time type : 3000 |
| ASRS Report | 433680 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Events | |
| Anomaly | non adherence : published procedure non adherence : clearance non adherence : far other anomaly other other spatial deviation |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance flight crew : became reoriented |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On departure from day airport via vectors, day 3 departure, we were given 210 degree heading (approximately) to intercept cvg 004 degree radial. I understood and read back '204 degree radial.' heading assignment did not work for a 204 degree radial, so, thinking the controller had given us the heading late, we turned to 180 degree heading to intercept. Once switched to center, they asked if we were assigned that heading and the miscom error became evident. Center kept us on that heading until cleared direct down the road. Original misunderstanding (204 degrees versus 004 degrees) compounded by FMC navigation page which showed 204 degrees inbound to cvg -- seemed to confirm misunderstood clearance. Solution: if clearance doesn't make sense, immediately question it. Don't try to make it work or let a coincidental navigation indication confirm a suspicious clearance.
Original NASA ASRS Text
Title: AN ACR FLC FLYING B737-300 FROM DAY READ BACK THE WRONG HDG INSTRUCTIONS TO ATC RESULTING IN A TRACK DEV.
Narrative: ON DEP FROM DAY ARPT VIA VECTORS, DAY 3 DEP, WE WERE GIVEN 210 DEG HDG (APPROX) TO INTERCEPT CVG 004 DEG RADIAL. I UNDERSTOOD AND READ BACK '204 DEG RADIAL.' HDG ASSIGNMENT DID NOT WORK FOR A 204 DEG RADIAL, SO, THINKING THE CTLR HAD GIVEN US THE HDG LATE, WE TURNED TO 180 DEG HDG TO INTERCEPT. ONCE SWITCHED TO CTR, THEY ASKED IF WE WERE ASSIGNED THAT HDG AND THE MISCOM ERROR BECAME EVIDENT. CTR KEPT US ON THAT HDG UNTIL CLRED DIRECT DOWN THE ROAD. ORIGINAL MISUNDERSTANDING (204 DEGS VERSUS 004 DEGS) COMPOUNDED BY FMC NAV PAGE WHICH SHOWED 204 DEGS INBOUND TO CVG -- SEEMED TO CONFIRM MISUNDERSTOOD CLRNC. SOLUTION: IF CLRNC DOESN'T MAKE SENSE, IMMEDIATELY QUESTION IT. DON'T TRY TO MAKE IT WORK OR LET A COINCIDENTAL NAV INDICATION CONFIRM A SUSPICIOUS CLRNC.
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.