37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 436020 |
Time | |
Date | 199904 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
State Reference | NY |
Altitude | msl single value : 16000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zbw.artcc |
Operator | common carrier : air carrier |
Make Model Name | Jetstream 32 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine pilot : commercial pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 6000 flight time type : 3000 |
ASRS Report | 436020 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : instrument |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : returned to original clearance |
Supplementary | |
Problem Areas | Company |
Primary Problem | Company |
Narrative:
On an 'as filed' route from syr to iad, we discovered we had been flying the wrong route. Flight plan route was syr-scipo-fqm-seg, however, the crew was interrupted from normal preflight checks by a passenger who was concerned about a close connection at iad (we were running late due to headwinds). Our new company FMS software that has preloaded flight plans had been installed on apr/ab/99, however, most of the flight plans are wrong and require the crew to edit them to the actual filed flight plan. Company management had published a directive that we would have data on flight release to select proper flight plan from the database without the need to edit manually. This data was never or had not been incorporated at this time. No conflict with other traffic or query from ATC as we discovered the error shortly before the controller cleared us to a downline fix. Interruptions from passenger are common, however, this new FMS flight plan software program and related data on flight releases was not completed as advertised by company management requiring crews to edit 9 out of 10 flight plans in the FMS to match filed rtes on the releases.
Original NASA ASRS Text
Title: MDT CREW FLEW WRONG RTE OF FLT.
Narrative: ON AN 'AS FILED' RTE FROM SYR TO IAD, WE DISCOVERED WE HAD BEEN FLYING THE WRONG RTE. FLT PLAN RTE WAS SYR-SCIPO-FQM-SEG, HOWEVER, THE CREW WAS INTERRUPTED FROM NORMAL PREFLT CHKS BY A PAX WHO WAS CONCERNED ABOUT A CLOSE CONNECTION AT IAD (WE WERE RUNNING LATE DUE TO HEADWINDS). OUR NEW COMPANY FMS SOFTWARE THAT HAS PRELOADED FLT PLANS HAD BEEN INSTALLED ON APR/AB/99, HOWEVER, MOST OF THE FLT PLANS ARE WRONG AND REQUIRE THE CREW TO EDIT THEM TO THE ACTUAL FILED FLT PLAN. COMPANY MGMNT HAD PUBLISHED A DIRECTIVE THAT WE WOULD HAVE DATA ON FLT RELEASE TO SELECT PROPER FLT PLAN FROM THE DATABASE WITHOUT THE NEED TO EDIT MANUALLY. THIS DATA WAS NEVER OR HAD NOT BEEN INCORPORATED AT THIS TIME. NO CONFLICT WITH OTHER TFC OR QUERY FROM ATC AS WE DISCOVERED THE ERROR SHORTLY BEFORE THE CTLR CLRED US TO A DOWNLINE FIX. INTERRUPTIONS FROM PAX ARE COMMON, HOWEVER, THIS NEW FMS FLT PLAN SOFTWARE PROGRAM AND RELATED DATA ON FLT RELEASES WAS NOT COMPLETED AS ADVERTISED BY COMPANY MGMNT REQUIRING CREWS TO EDIT 9 OUT OF 10 FLT PLANS IN THE FMS TO MATCH FILED RTES ON THE RELEASES.
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.