37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 201652 |
Time | |
Date | 199202 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : zoa |
State Reference | CA |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 3 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | climbout : takeoff ground : preflight ground other : taxi |
Route In Use | enroute : other oceanic enroute : pacific enroute airway : zoa |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel other personnel other |
Qualification | other |
ASRS Report | 201652 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Captain flight sfo/hnl called 2 hours prior to departure to discuss changing his route of flight due strong headwinds. I looked at new flight plan and we decided it was a fuel efficient route. I asked the captain to ask for a 'full route' clearance and noted it on the release. When the flight departure he received 'cleared as filed,' and flew what was on his release. Oakland oceanic called and questioned what his filing was and I told them what had happened. Our computer system automatically files flight plans 90 min prior to departure for us. When the captain called he was not filed. When I re-released his flight it was still 1 hour and 45 min prior to departure. The second flight plan should have been what was filed, but our computer system sent the incorrect flight plan. What I do whenever I change a route of flight I always ask the crew to call for a 'full readback clearance' just in case. But this time he did not. Our system needs to send us a strip back to our computer when a flight plan has been filed so we can double check.
Original NASA ASRS Text
Title: HDG TRACK POS DEV OCCURS WHEN ACR WDB FLIES COMPANY COMPUTER FLT PLAN AS OPPOSED TO FLT PLAN FILED FOR ATC.
Narrative: CAPT FLT SFO/HNL CALLED 2 HRS PRIOR TO DEP TO DISCUSS CHANGING HIS RTE OF FLT DUE STRONG HEADWINDS. I LOOKED AT NEW FLT PLAN AND WE DECIDED IT WAS A FUEL EFFICIENT RTE. I ASKED THE CAPT TO ASK FOR A 'FULL RTE' CLRNC AND NOTED IT ON THE RELEASE. WHEN THE FLT DEP HE RECEIVED 'CLRED AS FILED,' AND FLEW WHAT WAS ON HIS RELEASE. OAKLAND OCEANIC CALLED AND QUESTIONED WHAT HIS FILING WAS AND I TOLD THEM WHAT HAD HAPPENED. OUR COMPUTER SYS AUTOMATICALLY FILES FLT PLANS 90 MIN PRIOR TO DEP FOR US. WHEN THE CAPT CALLED HE WAS NOT FILED. WHEN I RE-RELEASED HIS FLT IT WAS STILL 1 HR AND 45 MIN PRIOR TO DEP. THE SECOND FLT PLAN SHOULD HAVE BEEN WHAT WAS FILED, BUT OUR COMPUTER SYS SENT THE INCORRECT FLT PLAN. WHAT I DO WHENEVER I CHANGE A RTE OF FLT I ALWAYS ASK THE CREW TO CALL FOR A 'FULL READBACK CLRNC' JUST IN CASE. BUT THIS TIME HE DID NOT. OUR SYS NEEDS TO SEND US A STRIP BACK TO OUR COMPUTER WHEN A FLT PLAN HAS BEEN FILED SO WE CAN DOUBLE CHK.
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.