 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 flight crew has a track/heading deviation while en route because an en route fix was not in the FMS database.
| Attributes | |
| ACN | 723497 |
| Time | |
| Date | 200701 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : zoa.artcc |
| State Reference | CA |
| Altitude | msl single value : 31000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-800 |
| 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 : multi engine pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 220 flight time total : 10500 flight time type : 1200 |
| ASRS Report | 723497 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp pilot : private |
| Experience | flight time last 90 days : 180 flight time total : 6500 flight time type : 500 |
| ASRS Report | 723874 |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Aircraft Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
The aircraft was late arriving in sjc due to snow in slc. As a result; we were in a rush to get the aircraft out to make an on-time departure. I checked the first officer's FMS programming of the route (he was the PF) up to the point of confirming the departure procedure and first couple of points. But I never got around to checking the full route. Our clearance was loupe 1.lin..jsica..ilc.J58.mlf. Apparently the first officer never programmed jsica into the route because after lin the aircraft proceeded direct to ilc. ZOA called us and questioned our routing and it was then that we discovered our error. Jsica was not in the database for our FMS and when he typed it in; he apparently got distraction and did not notice that the computer did not accept the input. After questioning our intentions as to our proposed route; oak cleared us direct to hbu and did not show any concern about our position relative to other aircraft. Supplemental information from acn 723874: as I checked the FMS we were flying to ilc. When we put in jsica in the FMS it was not in the database. When I loaded the FMS with the route of flight; I did not see this message on the ground. We ended up being south of course by approximately 5 mi. We had to manually put in the coordinates for jsica.
Original NASA ASRS Text
Title: B737-800 FLT CREW HAS A TRACK/HDG DEV WHILE ENRTE BECAUSE AN ENRTE FIX WAS NOT IN THE FMS DATABASE.
Narrative: THE ACFT WAS LATE ARRIVING IN SJC DUE TO SNOW IN SLC. AS A RESULT; WE WERE IN A RUSH TO GET THE ACFT OUT TO MAKE AN ON-TIME DEP. I CHKED THE FO'S FMS PROGRAMMING OF THE RTE (HE WAS THE PF) UP TO THE POINT OF CONFIRMING THE DEP PROC AND FIRST COUPLE OF POINTS. BUT I NEVER GOT AROUND TO CHKING THE FULL RTE. OUR CLRNC WAS LOUPE 1.LIN..JSICA..ILC.J58.MLF. APPARENTLY THE FO NEVER PROGRAMMED JSICA INTO THE RTE BECAUSE AFTER LIN THE ACFT PROCEEDED DIRECT TO ILC. ZOA CALLED US AND QUESTIONED OUR ROUTING AND IT WAS THEN THAT WE DISCOVERED OUR ERROR. JSICA WAS NOT IN THE DATABASE FOR OUR FMS AND WHEN HE TYPED IT IN; HE APPARENTLY GOT DISTR AND DID NOT NOTICE THAT THE COMPUTER DID NOT ACCEPT THE INPUT. AFTER QUESTIONING OUR INTENTIONS AS TO OUR PROPOSED RTE; OAK CLRED US DIRECT TO HBU AND DID NOT SHOW ANY CONCERN ABOUT OUR POS RELATIVE TO OTHER ACFT. SUPPLEMENTAL INFO FROM ACN 723874: AS I CHKED THE FMS WE WERE FLYING TO ILC. WHEN WE PUT IN JSICA IN THE FMS IT WAS NOT IN THE DATABASE. WHEN I LOADED THE FMS WITH THE RTE OF FLT; I DID NOT SEE THIS MESSAGE ON THE GND. WE ENDED UP BEING S OF COURSE BY APPROX 5 MI. WE HAD TO MANUALLY PUT IN THE COORDINATES FOR JSICA.
Data retrieved from NASA's ASRS site as of January 2009 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.