37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 361337 |
Time | |
Date | 199702 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : slc |
State Reference | UT |
Altitude | msl bound lower : 31000 msl bound upper : 31000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zlc |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other |
Route In Use | departure sid : sid enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 10000 flight time type : 400 |
ASRS Report | 361337 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 9000 flight time type : 3000 |
ASRS Report | 361639 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : far non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Filed flight plan was slc-mlf-J107-hector. The clearance was mlf 2 mlf-bld as filed. We were dealing with a recurring generator malfunction when we received the pre departure clearance. The first officer and I noted the difference between filed route and route clearance but I neglected to make the appropriate route adjustment in the FMS. After takeoff we received 2 vectors to intercept the departure. I armed the navigation capture mode and captured the outbound route (slc direct mlf). I did not xchk the raw data information so I did not notice the error. (The VOR radio and course were set correctly for the mlf 2 departure.) the ATC controller made us aware of the error and issued a vector for on course. I think a partial solution for this is for our operations department to file for the route ATC prefers rather than one that is never issued. This was typical of most incidents where a mechanical problem caused a distraction so that another task was ignored.
Original NASA ASRS Text
Title: ACR MLG HAD FILED SLC-MLF-J107-HEC. PDC WAS MLF 2 SID MLF-BLD AS FILED. FAILED TO REPROGRAM FMC. HAVING PROB WITH THE ELECTRICAL SYS AND FAILED TO DOUBLE CHK THE RAW DATA WITH FMC. CTLR VECTORED TO CLRED ROUTING.
Narrative: FILED FLT PLAN WAS SLC-MLF-J107-HECTOR. THE CLRNC WAS MLF 2 MLF-BLD AS FILED. WE WERE DEALING WITH A RECURRING GENERATOR MALFUNCTION WHEN WE RECEIVED THE PDC. THE FO AND I NOTED THE DIFFERENCE BTWN FILED RTE AND RTE CLRNC BUT I NEGLECTED TO MAKE THE APPROPRIATE RTE ADJUSTMENT IN THE FMS. AFTER TKOF WE RECEIVED 2 VECTORS TO INTERCEPT THE DEP. I ARMED THE NAV CAPTURE MODE AND CAPTURED THE OUTBOUND RTE (SLC DIRECT MLF). I DID NOT XCHK THE RAW DATA INFO SO I DID NOT NOTICE THE ERROR. (THE VOR RADIO AND COURSE WERE SET CORRECTLY FOR THE MLF 2 DEP.) THE ATC CTLR MADE US AWARE OF THE ERROR AND ISSUED A VECTOR FOR ON COURSE. I THINK A PARTIAL SOLUTION FOR THIS IS FOR OUR OPS DEPT TO FILE FOR THE RTE ATC PREFERS RATHER THAN ONE THAT IS NEVER ISSUED. THIS WAS TYPICAL OF MOST INCIDENTS WHERE A MECHANICAL PROB CAUSED A DISTR SO THAT ANOTHER TASK WAS IGNORED.
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.