37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 595428 |
Time | |
Date | 200309 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : lax.airport |
State Reference | CA |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air carrier |
Make Model Name | MD-11 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 25l ils other localizer other vortac |
Flight Phase | descent : approach descent : intermediate altitude |
Route In Use | approach : instrument precision arrival star : paradise |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 17200 flight time type : 2500 |
ASRS Report | 595428 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | aircraft equipment problem : less severe altitude deviation : crossing restriction not met non adherence : published procedure non adherence : company policies non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | aircraft : automation overrode flight crew flight crew : returned to intended or assigned course flight crew : overrode automation flight crew : became reoriented |
Supplementary | |
Problem Areas | Flight Crew Human Performance Chart Or Publication Airport ATC Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Flight departed gyr for lax. The company filed flight plan included a civet four arrival to lax. The crew inserted the civet four arrival into the FMS along with an anticipated approach to runway 24R. The flight proceeded normally until contacting socal approach, at which time we were reclred via the paradise four arrival. This was entered into the FMS and the flight proceeded normally. As we approached paradise VOR, we were told that we would land on runway 25L. The first officer entered runway 25L into the FMS, apparently without including the paradise arrival. With that entry, the arrival, with the important tejay and arnes intxns and their altitude restrs, dropped out of the flight plan program. As we were then approaching the paradise VOR, I, as PF, reverted to raw data and flew the 277 degree radial outbound. I instructed the first officer to reinsert the tejay and arnes intxns, but due to the slow reaction time of the FMS and the rapid progress of the flight, each input was realized only after passing the waypoints. This caused some confusion, as I was simultaneously overseeing the FMS programming and flying the aircraft. The result was that I was slow to intercept the runway 25L localizer, and overshot to the north. At that point, I concentrated fully on intercepting the localizer, which never reached full scale deflection, and then flying on the GS. The result was an inexact following of the arrival, and uncertainty of making all altitude restrs. Although I flew the final 30 mi of the approach on localizer and on glide path, the course of the arrival from paradise VOR to the arnes intersection was not flown precisely. I believe this was the result of inadvertently entering the approach and landing runway incorrectly, and then concentrating more on reentering the arrival into the FMS while not just flying the aircraft on raw data.
Original NASA ASRS Text
Title: AN MD11 PIC HAS A PROB WITH FOLLOWING THE PARADISE ARR PROC FLYING RAW DATA WHEN THE FO FAILS TO PROGRAM THE FMS PROPERLY FOR A RWY CHANGE TO RWY 25L AT LAX, CA.
Narrative: FLT DEPARTED GYR FOR LAX. THE COMPANY FILED FLT PLAN INCLUDED A CIVET FOUR ARR TO LAX. THE CREW INSERTED THE CIVET FOUR ARR INTO THE FMS ALONG WITH AN ANTICIPATED APCH TO RWY 24R. THE FLT PROCEEDED NORMALLY UNTIL CONTACTING SOCAL APCH, AT WHICH TIME WE WERE RECLRED VIA THE PARADISE FOUR ARR. THIS WAS ENTERED INTO THE FMS AND THE FLT PROCEEDED NORMALLY. AS WE APCHED PARADISE VOR, WE WERE TOLD THAT WE WOULD LAND ON RWY 25L. THE FO ENTERED RWY 25L INTO THE FMS, APPARENTLY WITHOUT INCLUDING THE PARADISE ARR. WITH THAT ENTRY, THE ARR, WITH THE IMPORTANT TEJAY AND ARNES INTXNS AND THEIR ALT RESTRS, DROPPED OUT OF THE FLT PLAN PROGRAM. AS WE WERE THEN APCHING THE PARADISE VOR, I, AS PF, REVERTED TO RAW DATA AND FLEW THE 277 DEG RADIAL OUTBOUND. I INSTRUCTED THE FO TO REINSERT THE TEJAY AND ARNES INTXNS, BUT DUE TO THE SLOW REACTION TIME OF THE FMS AND THE RAPID PROGRESS OF THE FLT, EACH INPUT WAS REALIZED ONLY AFTER PASSING THE WAYPOINTS. THIS CAUSED SOME CONFUSION, AS I WAS SIMULTANEOUSLY OVERSEEING THE FMS PROGRAMMING AND FLYING THE ACFT. THE RESULT WAS THAT I WAS SLOW TO INTERCEPT THE RWY 25L LOC, AND OVERSHOT TO THE N. AT THAT POINT, I CONCENTRATED FULLY ON INTERCEPTING THE LOC, WHICH NEVER REACHED FULL SCALE DEFLECTION, AND THEN FLYING ON THE GS. THE RESULT WAS AN INEXACT FOLLOWING OF THE ARR, AND UNCERTAINTY OF MAKING ALL ALT RESTRS. ALTHOUGH I FLEW THE FINAL 30 MI OF THE APCH ON LOC AND ON GLIDE PATH, THE COURSE OF THE ARR FROM PARADISE VOR TO THE ARNES INTXN WAS NOT FLOWN PRECISELY. I BELIEVE THIS WAS THE RESULT OF INADVERTENTLY ENTERING THE APCH AND LNDG RWY INCORRECTLY, AND THEN CONCENTRATING MORE ON REENTERING THE ARR INTO THE FMS WHILE NOT JUST FLYING THE ACFT ON RAW DATA.
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.