37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 195992 |
Time | |
Date | 199112 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : msp airport : dtw |
State Reference | MI |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Aircraft 1 | |
Controlling Facilities | tracon : shv |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 3 Turbojet Eng |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
Qualification | other |
ASRS Report | 195992 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Air Traffic Incident | Pilot Deviation |
Narrative:
I dispatched flight dtw-sfo, filed dbq.J94.lcu.J158.MVA. The flight plan route was dbq.J94.ocs.J154.slc.J56.MVA. At air carrier company the filed route and the flight plan route are independent of each other so this kind of error can occur. Unfortunately, the workload on the desk I was working prevented me from verifying that the filed route and the flight plan route were the same on the 44 releases done on this shift. In this instance the flight crew also missed the error and programmed their INS to fly the flight plan route while ATC thought they would be flying the filed route. Needless to say this is a safety issue. Our navigation database needs to be more intensely scrutinized, the computer system has to be enhanced to eliminate this kind of error or the workload adjusted so these errors can be found prior to flight.
Original NASA ASRS Text
Title: FLT PLAN CHANGE FROM ORIGINALLY FILED NOT PICKED UP BY DISPATCHER OR FLC.
Narrative: I DISPATCHED FLT DTW-SFO, FILED DBQ.J94.LCU.J158.MVA. THE FLT PLAN RTE WAS DBQ.J94.OCS.J154.SLC.J56.MVA. AT ACR COMPANY THE FILED RTE AND THE FLT PLAN RTE ARE INDEPENDENT OF EACH OTHER SO THIS KIND OF ERROR CAN OCCUR. UNFORTUNATELY, THE WORKLOAD ON THE DESK I WAS WORKING PREVENTED ME FROM VERIFYING THAT THE FILED RTE AND THE FLT PLAN RTE WERE THE SAME ON THE 44 RELEASES DONE ON THIS SHIFT. IN THIS INSTANCE THE FLC ALSO MISSED THE ERROR AND PROGRAMMED THEIR INS TO FLY THE FLT PLAN RTE WHILE ATC THOUGHT THEY WOULD BE FLYING THE FILED RTE. NEEDLESS TO SAY THIS IS A SAFETY ISSUE. OUR NAV DATABASE NEEDS TO BE MORE INTENSELY SCRUTINIZED, THE COMPUTER SYS HAS TO BE ENHANCED TO ELIMINATE THIS KIND OF ERROR OR THE WORKLOAD ADJUSTED SO THESE ERRORS CAN BE FOUND PRIOR TO FLT.
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.