37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 391330 |
Time | |
Date | 199801 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : vny |
State Reference | CA |
Altitude | msl bound lower : 7000 msl bound upper : 7000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sna |
Operator | general aviation : corporate |
Make Model Name | Super King Air 300 |
Operating Under FAR Part | Part 91 |
Navigation In Use | Other |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 16000 flight time type : 450 |
ASRS Report | 391330 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : far non adherence : clearance other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : overcame equipment problem other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This incident involved an IFR tower to tower flight from vny to lgb using the published routing. When reviewing the los angeles IFR area chart prior to flight, for some reason which I cannot explain, I failed to notice the intersection of V186 and V394 (adamm) and thought the routing required continuing to pdz VOR then wbound to sli VOR. This is exactly what I did while flying the route. To prevent ATC from bringing this to my attention, at some point, very near adamm intersection, communications failure (my receiver I assume) occurred. I realized this near pdz VOR and re-established communications on another frequency. At this point I also realized my error in routing. More diligence in preflight and in-flight planning is the most significant factor in preventing a recurrence of this type of incident. I find it somewhat more stressful flying routes which are prescribed than those which I planned myself. Unfamiliarity with the particular route also affected the process. I am very familiar with V186 and the elmoo departure continuing on to pdz VOR and this also may have contributed to my flawed thought process.
Original NASA ASRS Text
Title: A CPR FLC IN A BE30 FLEW THROUGH A TURN POINT AND GOT OFF COURSE.
Narrative: THIS INCIDENT INVOLVED AN IFR TWR TO TWR FLT FROM VNY TO LGB USING THE PUBLISHED ROUTING. WHEN REVIEWING THE LOS ANGELES IFR AREA CHART PRIOR TO FLT, FOR SOME REASON WHICH I CANNOT EXPLAIN, I FAILED TO NOTICE THE INTXN OF V186 AND V394 (ADAMM) AND THOUGHT THE ROUTING REQUIRED CONTINUING TO PDZ VOR THEN WBOUND TO SLI VOR. THIS IS EXACTLY WHAT I DID WHILE FLYING THE RTE. TO PREVENT ATC FROM BRINGING THIS TO MY ATTN, AT SOME POINT, VERY NEAR ADAMM INTXN, COMS FAILURE (MY RECEIVER I ASSUME) OCCURRED. I REALIZED THIS NEAR PDZ VOR AND RE-ESTABLISHED COMS ON ANOTHER FREQ. AT THIS POINT I ALSO REALIZED MY ERROR IN ROUTING. MORE DILIGENCE IN PREFLT AND INFLT PLANNING IS THE MOST SIGNIFICANT FACTOR IN PREVENTING A RECURRENCE OF THIS TYPE OF INCIDENT. I FIND IT SOMEWHAT MORE STRESSFUL FLYING ROUTES WHICH ARE PRESCRIBED THAN THOSE WHICH I PLANNED MYSELF. UNFAMILIARITY WITH THE PARTICULAR RTE ALSO AFFECTED THE PROCESS. I AM VERY FAMILIAR WITH V186 AND THE ELMOO DEP CONTINUING ON TO PDZ VOR AND THIS ALSO MAY HAVE CONTRIBUTED TO MY FLAWED THOUGHT PROCESS.
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.