 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of air carrier medium large transport aircraft inadvertently deviated from the SID departure assigned.
| Attributes | |
| ACN | 229216 |
| Time | |
| Date | 199212 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : sea |
| State Reference | WA |
| Altitude | msl bound lower : 5000 msl bound upper : 5000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : sea tower : mem |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | departure other departure sid : sid |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : flight engineer pilot : commercial |
| Experience | flight time last 90 days : 200 flight time total : 3500 flight time type : 900 |
| ASRS Report | 229216 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 250 flight time total : 8000 flight time type : 85 |
| ASRS Report | 229337 |
| Events | |
| Anomaly | non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Takeoff from runway 16L was normal, climb out commenced on runway heading. We were anticipating radar vectors to intercept sea J70 elmaa, etc, which was the route listed on the pre departure clearance message crosschecked against our filed flight plan. Seattle departure questioned us if we were in the turn. We replied negative, we were runway heading expecting vectors. The portion of the pre departure clearance message containing the rtw was again referenced, and it reflected our filed route of sea J70 elmaa, with no mentioned of any SID. Departure then questioned which SID we were assigned. Again referencing the pre departure clearance message, we noticed that the elmaa 3 departure was listed, however, it was printed on the top portion of the pre departure clearance message, not near the route lines which are always on the bottom portion of the message. Other airports place the assigned SID on the bottom of the pre departure clearance message at the start of the assigned routing. The placement of the SID in the portion of the pre departure clearance message reserved for remarks caused both pilots to believe no SID was assigned, since normal habit patterns for both pilots xchking of filed routing versus assigned routing did not encompass reference to the remarks portion of the pre departure clearance message.
Original NASA ASRS Text
Title: FLC OF ACR MLG ACFT INADVERTENTLY DEVIATED FROM THE SID DEP ASSIGNED.
Narrative: TKOF FROM RWY 16L WAS NORMAL, CLBOUT COMMENCED ON RWY HDG. WE WERE ANTICIPATING RADAR VECTORS TO INTERCEPT SEA J70 ELMAA, ETC, WHICH WAS THE RTE LISTED ON THE PDC MESSAGE XCHKED AGAINST OUR FILED FLT PLAN. SEATTLE DEP QUESTIONED US IF WE WERE IN THE TURN. WE REPLIED NEGATIVE, WE WERE RWY HDG EXPECTING VECTORS. THE PORTION OF THE PDC MESSAGE CONTAINING THE RTW WAS AGAIN REFED, AND IT REFLECTED OUR FILED RTE OF SEA J70 ELMAA, WITH NO MENTIONED OF ANY SID. DEP THEN QUESTIONED WHICH SID WE WERE ASSIGNED. AGAIN REFING THE PDC MESSAGE, WE NOTICED THAT THE ELMAA 3 DEP WAS LISTED, HOWEVER, IT WAS PRINTED ON THE TOP PORTION OF THE PDC MESSAGE, NOT NEAR THE RTE LINES WHICH ARE ALWAYS ON THE BOTTOM PORTION OF THE MESSAGE. OTHER ARPTS PLACE THE ASSIGNED SID ON THE BOTTOM OF THE PDC MESSAGE AT THE START OF THE ASSIGNED ROUTING. THE PLACEMENT OF THE SID IN THE PORTION OF THE PDC MESSAGE RESERVED FOR REMARKS CAUSED BOTH PLTS TO BELIEVE NO SID WAS ASSIGNED, SINCE NORMAL HABIT PATTERNS FOR BOTH PLTS XCHKING OF FILED ROUTING VERSUS ASSIGNED ROUTING DID NOT ENCOMPASS REF TO THE REMARKS PORTION OF THE PDC MESSAGE.
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.