B737 flight crew fails to recognize revised clearance on pre departure clearance. Error is detected before course deviation can occur and correct SID is entered in FMC.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	787868
Time
Date	200805
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon tower : zzz.tower
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : initial
Route In Use	departure sid : loop
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 184 flight time type : 7500
ASRS Report	787868
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 250
ASRS Report	787867
Events
Anomaly	non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Company Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were cleared via the pre departure clearance the OSHNN3 dag. We thought we were cleared on the LOOP4 dag. This is how it is on the FMC: flight company #/ lax ZZZ pre departure clearance company #/ lax B/737/left 370 -OSHNN3 dag- lax LOOP4 dag las J146 hbu edct. This is very confusing. We are used to reading a clearance straight across; not on two different lines. When we get a pre departure clearance clearance that is different from the one on the release; both should not be shown on the CDU. First tower cleared us for takeoff with a heading of 210; this not being cleared for an RNAV departure. Also; lax tower used to ask the crew for the first fix. If this is no longer being done; then it should be. It would have prevented this from ever happening. Departure cleared us to pevee and the OSHNN3. On climb out is not the time to begin trying to reload the CDU. Also; departure said that they never issue the LOOP4 before XA00L; so why is dispatch filing us this way? He also said that company is doing this a lot. I suspect this is because of the way the clearance is being depicted on the CDU. If this possibility has not been brought to everybody's attention; then should be.

Original NASA ASRS Text

Title: B737 FLT CREW FAILS TO RECOGNIZE REVISED CLRNC ON PDC. ERROR IS DETECTED BEFORE COURSE DEV CAN OCCUR AND CORRECT SID IS ENTERED IN FMC.

Narrative: WE WERE CLEARED VIA THE PDC THE OSHNN3 DAG. WE THOUGHT WE WERE CLEARED ON THE LOOP4 DAG. THIS IS HOW IT IS ON THE FMC: FLIGHT COMPANY #/ LAX ZZZ PDC COMPANY #/ LAX B/737/L 370 -OSHNN3 DAG- LAX LOOP4 DAG LAS J146 HBU EDCT. THIS IS VERY CONFUSING. WE ARE USED TO READING A CLRNC STRAIGHT ACROSS; NOT ON TWO DIFFERENT LINES. WHEN WE GET A PDC CLRNC THAT IS DIFFERENT FROM THE ONE ON THE RELEASE; BOTH SHOULD NOT BE SHOWN ON THE CDU. FIRST TOWER CLEARED US FOR TAKEOFF WITH A HEADING OF 210; THIS NOT BEING CLEARED FOR AN RNAV DEP. ALSO; LAX TOWER USED TO ASK THE CREW FOR THE FIRST FIX. IF THIS IS NO LONGER BEING DONE; THEN IT SHOULD BE. IT WOULD HAVE PREVENTED THIS FROM EVER HAPPENING. DEP CLEARED US TO PEVEE AND THE OSHNN3. ON CLBOUT IS NOT THE TIME TO BEGIN TRYING TO RELOAD THE CDU. ALSO; DEP SAID THAT THEY NEVER ISSUE THE LOOP4 BEFORE XA00L; SO WHY IS DISPATCH FILING US THIS WAY? HE ALSO SAID THAT COMPANY IS DOING THIS A LOT. I SUSPECT THIS IS BECAUSE OF THE WAY THE CLRNC IS BEING DEPICTED ON THE CDU. IF THIS POSSIBILITY HAS NOT BEEN BROUGHT TO EVERYBODY'S ATTENTION; THEN SHOULD BE.

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.