37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 111886 |
Time | |
Date | 198905 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : slc |
State Reference | UT |
Altitude | msl bound lower : 7000 msl bound upper : 8000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : slc |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : sid |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 8500 |
ASRS Report | 111866 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Chart Or Publication |
Air Traffic Incident | Pilot Deviation |
Narrative:
On departure out of slc we were cleared to depart via the slc 3, then as filed; climb to 8000' and contact departure control on 126.8, squawking code. It was my leg as copilot and I misread the departure plate in that I read the lost communications instructions versus the normal departure instructions for runway 34L. Passing 7500' in a turn back toward the slc VORTAC the departure controller asked us to state our intentions. We replied we were flying the SID and recognized about the same time the controller did that we were flying the lost communications procedure. The situation was resolved by an on course vector from the controller with no apparent traffic conflict. Human performance considerations: in retrospect, as I reexamined the SID involved and looked at others, I realized that very few departures include los communication procedures. The ones that do have a hash-marked 'iiiiiii' line around the los communication section. On the slc 3 SID the hash markings are above a plan view of the procedure and this, I believe, contributed to my error.I would like to see the 'IIII' hash marks moved down around the actual los communication procedure verbage. I believe this would help prevent confusion by someone else.
Original NASA ASRS Text
Title: FLT CREW OF LGT DEPARTING SLC 3 SID MISREAD CHART AND WERE FOLLOWING LOST COM PROC UNTIL DEPARTURE CTLR INTERVENED.
Narrative: ON DEP OUT OF SLC WE WERE CLRED TO DEPART VIA THE SLC 3, THEN AS FILED; CLB TO 8000' AND CONTACT DEP CTL ON 126.8, SQUAWKING CODE. IT WAS MY LEG AS COPLT AND I MISREAD THE DEP PLATE IN THAT I READ THE LOST COMS INSTRUCTIONS VERSUS THE NORMAL DEP INSTRUCTIONS FOR RWY 34L. PASSING 7500' IN A TURN BACK TOWARD THE SLC VORTAC THE DEP CTLR ASKED US TO STATE OUR INTENTIONS. WE REPLIED WE WERE FLYING THE SID AND RECOGNIZED ABOUT THE SAME TIME THE CTLR DID THAT WE WERE FLYING THE LOST COMS PROC. THE SITUATION WAS RESOLVED BY AN ON COURSE VECTOR FROM THE CTLR WITH NO APPARENT TFC CONFLICT. HUMAN PERFORMANCE CONSIDERATIONS: IN RETROSPECT, AS I REEXAMINED THE SID INVOLVED AND LOOKED AT OTHERS, I REALIZED THAT VERY FEW DEPS INCLUDE LOS COM PROCS. THE ONES THAT DO HAVE A HASH-MARKED 'IIIIIII' LINE AROUND THE LOS COM SECTION. ON THE SLC 3 SID THE HASH MARKINGS ARE ABOVE A PLAN VIEW OF THE PROC AND THIS, I BELIEVE, CONTRIBUTED TO MY ERROR.I WOULD LIKE TO SEE THE 'IIII' HASH MARKS MOVED DOWN AROUND THE ACTUAL LOS COM PROC VERBAGE. I BELIEVE THIS WOULD HELP PREVENT CONFUSION BY SOMEONE ELSE.
Data retrieved from NASA's ASRS site as of August 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.