37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 228474 |
Time | |
Date | 199212 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : trm |
State Reference | CA |
Altitude | msl bound lower : 22700 msl bound upper : 27000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla |
Operator | general aviation : corporate |
Make Model Name | Medium Transport |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 50 flight time total : 11000 flight time type : 2000 |
ASRS Report | 228474 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 75 flight time total : 8300 flight time type : 2500 |
ASRS Report | 228383 |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
ATC had cleared us 'as filed.' flight plan number F had been selected as our desired flight plan but dispatch (flight plan service company) mistakenly filed flight plan number G. We thought that we had been cleared kcrq jli-trm-J236 tbc, J128 dbq, gij, J554 crl, J584 slt, dny.valrel-hpn. ZLA showed our active flight plan as: kcrq-jli-trm-J134 elsto, J105 noris, J96 jot J146 gij, J554 crl, J586 yxu, J94 buf, J16 hankk, dny vallre-hpn. ZLA asked if we were going direct to drk. I told them that we had been cleared via J236 over tbc. At that point we verified the assigned routing with ZLA and found the error. Flight plan service company was notified of the mistake and is tracking down the cause. A partial route readback with crq ground could have caught this error earlier. Also global data center could list the flight plan number in the remarks section. The flight crew could confirm the route by saying, 'cleared as filed' and then confirm the flight plan number.
Original NASA ASRS Text
Title: FLC OF ACR MDT ACFT INADVERTENTLY DEVIATED FROM ASSIGNED TRACK DUE TO FOLLOWING A PROPOSED RTE AND NOT THE RTE TO WHICH CLRED.
Narrative: ATC HAD CLRED US 'AS FILED.' FLT PLAN NUMBER F HAD BEEN SELECTED AS OUR DESIRED FLT PLAN BUT DISPATCH (FLT PLAN SVC COMPANY) MISTAKENLY FILED FLT PLAN NUMBER G. WE THOUGHT THAT WE HAD BEEN CLRED KCRQ JLI-TRM-J236 TBC, J128 DBQ, GIJ, J554 CRL, J584 SLT, DNY.VALREL-HPN. ZLA SHOWED OUR ACTIVE FLT PLAN AS: KCRQ-JLI-TRM-J134 ELSTO, J105 NORIS, J96 JOT J146 GIJ, J554 CRL, J586 YXU, J94 BUF, J16 HANKK, DNY VALLRE-HPN. ZLA ASKED IF WE WERE GOING DIRECT TO DRK. I TOLD THEM THAT WE HAD BEEN CLRED VIA J236 OVER TBC. AT THAT POINT WE VERIFIED THE ASSIGNED ROUTING WITH ZLA AND FOUND THE ERROR. FLT PLAN SVC COMPANY WAS NOTIFIED OF THE MISTAKE AND IS TRACKING DOWN THE CAUSE. A PARTIAL RTE READBACK WITH CRQ GND COULD HAVE CAUGHT THIS ERROR EARLIER. ALSO GLOBAL DATA CTR COULD LIST THE FLT PLAN NUMBER IN THE REMARKS SECTION. THE FLC COULD CONFIRM THE RTE BY SAYING, 'CLRED AS FILED' AND THEN CONFIRM THE FLT PLAN NUMBER.
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.