37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 794536 |
Time | |
Date | 200807 |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | airport : sfo.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | MD-83 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 794536 |
Events | |
Anomaly | aircraft equipment problem : critical |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : overrode automation flight crew : overcame equipment problem |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
First officer had loaded position and I checked it on the position page versus my 10-9 sfo plate. I swear that I saw the correct coords and then I loaded the route. Checked the progress page and mileage was off about 90 mi out but I thought that wasn't that unusual. Checked the legs pages and we actually discussed the new high altitude route structure fixes as the first officer was newly recalled and had not seen these before. I checked my distance on these fixes as a backup to avoid any input error. Legs page checked ok. However; as the first officer asked about the navigation display check just prior to takeoff I could not see the runway displayed because I was in a high range and the egpws display was cluttering the display. The departure was not an RNAV departure and we had discussed the routing before we taxied; that was a good thing because the FMS was off and I did not catch it just prior to takeoff. I had always thought that FMS aircraft updated their position as the throttles were advanced so I thought we would be ok. We were not. At rotation we got a terrain warning that continued for several seconds and the first officer flew the departure with the VOR information that we had discussed earlier. I advised departure control that we were unable to fly RNAV routing and they coordinated with center. The trip continued to ZZZ uneventfully. We reviewed everything we had done on the preflight and I can remember checking the 10-9 page with the position page; N37 37 and W122 22 stuck in my mind. The departure runway 1R was correct; the SID was correct; the transition was correct. The only thing I can possibly see being wrong was the initial position entered into the FMS and I thought I had checked that myself. I did fail to check the runway display just prior to takeoff and that surely allowed this situation to occur. Just because you think you put everything in correctly and had checked it before takeoff does not mean you don't have to check that runway display. The first officer did his job just fine; it appears that I didn't.
Original NASA ASRS Text
Title: MD80 FLT CREW TAKES OFF WITH INCORRECT PRESENT POSITION LAT/LONGS IN FMS. CONTINUES TO DESTINATION USING ALTERNATE NAV SYSTEMS.
Narrative: FO HAD LOADED POS AND I CHKED IT ON THE POS PAGE VERSUS MY 10-9 SFO PLATE. I SWEAR THAT I SAW THE CORRECT COORDS AND THEN I LOADED THE RTE. CHKED THE PROGRESS PAGE AND MILEAGE WAS OFF ABOUT 90 MI OUT BUT I THOUGHT THAT WASN'T THAT UNUSUAL. CHKED THE LEGS PAGES AND WE ACTUALLY DISCUSSED THE NEW HIGH ALT RTE STRUCTURE FIXES AS THE FO WAS NEWLY RECALLED AND HAD NOT SEEN THESE BEFORE. I CHKED MY DISTANCE ON THESE FIXES AS A BACKUP TO AVOID ANY INPUT ERROR. LEGS PAGE CHKED OK. HOWEVER; AS THE FO ASKED ABOUT THE NAV DISPLAY CHK JUST PRIOR TO TKOF I COULD NOT SEE THE RWY DISPLAYED BECAUSE I WAS IN A HIGH RANGE AND THE EGPWS DISPLAY WAS CLUTTERING THE DISPLAY. THE DEP WAS NOT AN RNAV DEP AND WE HAD DISCUSSED THE ROUTING BEFORE WE TAXIED; THAT WAS A GOOD THING BECAUSE THE FMS WAS OFF AND I DID NOT CATCH IT JUST PRIOR TO TKOF. I HAD ALWAYS THOUGHT THAT FMS ACFT UPDATED THEIR POS AS THE THROTTLES WERE ADVANCED SO I THOUGHT WE WOULD BE OK. WE WERE NOT. AT ROTATION WE GOT A TERRAIN WARNING THAT CONTINUED FOR SEVERAL SECONDS AND THE FO FLEW THE DEP WITH THE VOR INFO THAT WE HAD DISCUSSED EARLIER. I ADVISED DEP CTL THAT WE WERE UNABLE TO FLY RNAV ROUTING AND THEY COORDINATED WITH CTR. THE TRIP CONTINUED TO ZZZ UNEVENTFULLY. WE REVIEWED EVERYTHING WE HAD DONE ON THE PREFLT AND I CAN REMEMBER CHKING THE 10-9 PAGE WITH THE POS PAGE; N37 37 AND W122 22 STUCK IN MY MIND. THE DEP RWY 1R WAS CORRECT; THE SID WAS CORRECT; THE TRANSITION WAS CORRECT. THE ONLY THING I CAN POSSIBLY SEE BEING WRONG WAS THE INITIAL POS ENTERED INTO THE FMS AND I THOUGHT I HAD CHKED THAT MYSELF. I DID FAIL TO CHK THE RWY DISPLAY JUST PRIOR TO TKOF AND THAT SURELY ALLOWED THIS SITUATION TO OCCUR. JUST BECAUSE YOU THINK YOU PUT EVERYTHING IN CORRECTLY AND HAD CHKED IT BEFORE TKOF DOES NOT MEAN YOU DON'T HAVE TO CHK THAT RWY DISPLAY. THE FO DID HIS JOB JUST FINE; IT APPEARS THAT I DIDN'T.
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.