![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 784415 |
| Time | |
| Date | 200804 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : lax.airport |
| State Reference | CA |
| Altitude | msl single value : 7000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : sct.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 199 |
| ASRS Report | 784415 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : departure controller : radar |
| Events | |
| Anomaly | non adherence : clearance |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : returned to intended or assigned course |
| Supplementary | |
| Problem Areas | Chart Or Publication ATC Human Performance Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
Dispatch release said non-standard routing; but still filed on loop departure. First officer got pre departure clearance and missed a change to departure SID. Wording said - oshnn 3 - ; then next line said lax loop 4 dag J9 mlf delta 2 slc. Perhaps confusion expecting to see loop departure; and there it was. I never looked at pre departure clearance pg; and also was expecting loop; so did not question flight brief item on departure clearance. On departure; being vectored by socal; they then cleared us to point on oshnn departure. As pm I said we were on loop. They said should be on oshnn. They gave us another vector; told us to set up for oshnn; and then cleared us to sli on oshnn. Nothing more said. No deviations; just expecting vectors to a different departure. More attention to detail; especially when 'non standard routing' is on flight plan.
Original NASA ASRS Text
Title: FLT CREW FAIL TO FULLY READ PDC CLRNC. DEP CTLR RE-CLEARS.
Narrative: DISPATCH RELEASE SAID NON-STD ROUTING; BUT STILL FILED ON LOOP DEPARTURE. FO GOT PDC AND MISSED A CHANGE TO DEP SID. WORDING SAID - OSHNN 3 - ; THEN NEXT LINE SAID LAX LOOP 4 DAG J9 MLF DELTA 2 SLC. PERHAPS CONFUSION EXPECTING TO SEE LOOP DEPARTURE; AND THERE IT WAS. I NEVER LOOKED AT PDC PG; AND ALSO WAS EXPECTING LOOP; SO DID NOT QUESTION FLIGHT BRIEF ITEM ON DEPARTURE CLEARANCE. ON DEPARTURE; BEING VECTORED BY SOCAL; THEY THEN CLEARED US TO POINT ON OSHNN DEPARTURE. AS PM I SAID WE WERE ON LOOP. THEY SAID SHOULD BE ON OSHNN. THEY GAVE US ANOTHER VECTOR; TOLD US TO SET UP FOR OSHNN; AND THEN CLEARED US TO SLI ON OSHNN. NOTHING MORE SAID. NO DEVIATIONS; JUST EXPECTING VECTORS TO A DIFFERENT DEPARTURE. MORE ATTENTION TO DETAIL; ESPECIALLY WHEN 'NON STD ROUTING' IS ON FLIGHT PLAN.
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.