37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 510790 |
Time | |
Date | 200105 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : sck.tracon |
State Reference | CA |
Altitude | msl single value : 9500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : mke.tower |
Operator | common carrier : air carrier |
Make Model Name | Skyhawk 172/Cutlass 172 |
Flight Phase | cruise : level |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 12 flight time total : 17000 flight time type : 503 |
ASRS Report | 510790 |
Events | |
Anomaly | non adherence : far non adherence : published procedure other spatial deviation |
Resolutory Action | controller : issued alert |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Filed a VFR flight plan for toa-controller in charge at 9500 ft, using the same altitude selection gauge I have used for 35 yrs. Got it backwards this time -- should have been even, +500 ft. Was finally called to my attention after several frequency changes and I asked the controllers 'are you sure?' (assuming I was correct.) a momentary thought process produced the universal pilot response to the 'light bulb' moment 'oh shit!' what happened? I planned this flight and filed using my pc while too many other things occupied my attention. I have done it so many times, I took it all for granted even when rechking the printed copy. How to avoid? Don't take anything for granted. Examine each aspect of the plan, time, TAS, fuel burn, winds, individually and ask yourself 'is this ok to pass a check ride?' suggestion for someone: I filed this plan using duats. I'm not trying to excuse my own error, however, could not the duats software be tweaked to catch an odd 'altitude, +500 ft' for a VFR flight plan heading west? Human performance factor: complacency.
Original NASA ASRS Text
Title: AFTER PREFLT PLANNING, DUATS PROCESSING, AND FLT PLAN REVIEW, C172 PLT OVERLOOKS CORRECT ALT FOR DIRECTION OF FLT, WHICH IS CORRECTED BY SCK APCH.
Narrative: FILED A VFR FLT PLAN FOR TOA-CIC AT 9500 FT, USING THE SAME ALT SELECTION GAUGE I HAVE USED FOR 35 YRS. GOT IT BACKWARDS THIS TIME -- SHOULD HAVE BEEN EVEN, +500 FT. WAS FINALLY CALLED TO MY ATTN AFTER SEVERAL FREQ CHANGES AND I ASKED THE CTLRS 'ARE YOU SURE?' (ASSUMING I WAS CORRECT.) A MOMENTARY THOUGHT PROCESS PRODUCED THE UNIVERSAL PLT RESPONSE TO THE 'LIGHT BULB' MOMENT 'OH SHIT!' WHAT HAPPENED? I PLANNED THIS FLT AND FILED USING MY PC WHILE TOO MANY OTHER THINGS OCCUPIED MY ATTN. I HAVE DONE IT SO MANY TIMES, I TOOK IT ALL FOR GRANTED EVEN WHEN RECHKING THE PRINTED COPY. HOW TO AVOID? DON'T TAKE ANYTHING FOR GRANTED. EXAMINE EACH ASPECT OF THE PLAN, TIME, TAS, FUEL BURN, WINDS, INDIVIDUALLY AND ASK YOURSELF 'IS THIS OK TO PASS A CHK RIDE?' SUGGESTION FOR SOMEONE: I FILED THIS PLAN USING DUATS. I'M NOT TRYING TO EXCUSE MY OWN ERROR, HOWEVER, COULD NOT THE DUATS SOFTWARE BE TWEAKED TO CATCH AN ODD 'ALT, +500 FT' FOR A VFR FLT PLAN HDG W? HUMAN PERFORMANCE FACTOR: COMPLACENCY.
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.