 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
While enroute; a B767 flight crew programmed the arrival into the FMC; but several waypoints were missing.
| Attributes | |
| ACN | 777656 |
| Time | |
| Date | 200803 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : zla.airport |
| State Reference | CA |
| Altitude | msl single value : 39000 |
| Aircraft 1 | |
| Controlling Facilities | artcc : zla.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 777656 |
| Events | |
| Anomaly | aircraft equipment problem : less severe other anomaly other |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Aircraft |
| Primary Problem | Aircraft |
Narrative:
A preflight of the FMC initial page was checked for the correct active navigation data date; operations program and engine type. En route; the FMC was programmed to fly the seavu 2 arrival to lax. Upon checking the arrival waypoints; several points were missing. Reprogramming the FMC did not correct the problem. An attempt to manually input the missing waypoints was made and the FMC message read 'not in navigation database.' rechking the FMC initial page it was noted that the navigation data was number off by 1 digit. An uneventful arrival was made using raw data. Although the active date of the navigation data was checked I failed to recognize the proper navigation data software program. In the future; careful attention must be given to checking the navigation data software program. Callback conversation with reporter revealed the following information: the reporter stated that the company had issued a bulletin with regard to this software package; but complying with the bulletin had no positive effect. Updated software has since been installed; and the navigation problems were corrected.
Original NASA ASRS Text
Title: WHILE ENROUTE; A B767 FLT CREW PROGRAMMED THE ARRIVAL INTO THE FMC; BUT SEVERAL WAYPOINTS WERE MISSING.
Narrative: A PREFLT OF THE FMC INITIAL PAGE WAS CHKED FOR THE CORRECT ACTIVE NAV DATA DATE; OPS PROGRAM AND ENG TYPE. ENRTE; THE FMC WAS PROGRAMMED TO FLY THE SEAVU 2 ARR TO LAX. UPON CHKING THE ARR WAYPOINTS; SEVERAL POINTS WERE MISSING. REPROGRAMMING THE FMC DID NOT CORRECT THE PROB. AN ATTEMPT TO MANUALLY INPUT THE MISSING WAYPOINTS WAS MADE AND THE FMC MESSAGE READ 'NOT IN NAV DATABASE.' RECHKING THE FMC INITIAL PAGE IT WAS NOTED THAT THE NAV DATA WAS NUMBER OFF BY 1 DIGIT. AN UNEVENTFUL ARR WAS MADE USING RAW DATA. ALTHOUGH THE ACTIVE DATE OF THE NAV DATA WAS CHKED I FAILED TO RECOGNIZE THE PROPER NAV DATA SOFTWARE PROGRAM. IN THE FUTURE; CAREFUL ATTN MUST BE GIVEN TO CHKING THE NAV DATA SOFTWARE PROGRAM. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE REPORTER STATED THAT THE COMPANY HAD ISSUED A BULLETIN WITH REGARD TO THIS SOFTWARE PACKAGE; BUT COMPLYING WITH THE BULLETIN HAD NO POSITIVE EFFECT. UPDATED SOFTWARE HAS SINCE BEEN INSTALLED; AND THE NAV PROBLEMS WERE CORRECTED.
Data retrieved from NASA's ASRS site as of May 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.