A B737-300 flight crew on the civet 5 arrival to lax got a last min runway change from runway 24R to runway 25R. They failed to load the transition; and missed a crossing restr at fallt intersection.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	709288
Time
Date	200609
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl bound lower : 4000 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : civet5
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 295 flight time type : 8000
ASRS Report	709288
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 244 flight time type : 3500
ASRS Report	709287
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Inbound to lax got speed reduction for traffic and a few vectors off course for spacing. Had programmed into CDU; civet arrival and runway 24R. Received a change during arrival to runway 25R. This is the first time I had been to the runway 25R runway. We reprogrammed into the CDU the civet arrival and runway 25R. Executed the box and the intersection fallt did not come up when closing the route. Missed it during the approach. Controller said there was no problem; but to watch it the next time. No other traffic was moved due to the missed altitude. After looking at the problem on the ground; found out that you must select the arrival; the transition and runway and you must also select the runway transition; in order to get the intersection fallt to be input on the screen. If you forget the runway transition; the intersection fallt does not come up for display. This is what happened to us; and we missed the intersection at 5000 ft. Need to back up the approach using both the paper chart and the box. Use both; not just one system by itself.

Original NASA ASRS Text

Title: A B737-300 FLT CREW ON THE CIVET 5 ARR TO LAX GOT A LAST MIN RWY CHANGE FROM RWY 24R TO RWY 25R. THEY FAILED TO LOAD THE TRANSITION; AND MISSED A XING RESTR AT FALLT INTXN.

Narrative: INBOUND TO LAX GOT SPD REDUCTION FOR TFC AND A FEW VECTORS OFF COURSE FOR SPACING. HAD PROGRAMMED INTO CDU; CIVET ARR AND RWY 24R. RECEIVED A CHANGE DURING ARR TO RWY 25R. THIS IS THE FIRST TIME I HAD BEEN TO THE RWY 25R RWY. WE REPROGRAMMED INTO THE CDU THE CIVET ARR AND RWY 25R. EXECUTED THE BOX AND THE INTXN FALLT DID NOT COME UP WHEN CLOSING THE RTE. MISSED IT DURING THE APCH. CTLR SAID THERE WAS NO PROB; BUT TO WATCH IT THE NEXT TIME. NO OTHER TFC WAS MOVED DUE TO THE MISSED ALT. AFTER LOOKING AT THE PROB ON THE GND; FOUND OUT THAT YOU MUST SELECT THE ARR; THE TRANSITION AND RWY AND YOU MUST ALSO SELECT THE RWY TRANSITION; IN ORDER TO GET THE INTXN FALLT TO BE INPUT ON THE SCREEN. IF YOU FORGET THE RWY TRANSITION; THE INTXN FALLT DOES NOT COME UP FOR DISPLAY. THIS IS WHAT HAPPENED TO US; AND WE MISSED THE INTXN AT 5000 FT. NEED TO BACK UP THE APCH USING BOTH THE PAPER CHART AND THE BOX. USE BOTH; NOT JUST ONE SYS BY ITSELF.

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.