37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 202081 |
Time | |
Date | 199202 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : eno |
State Reference | DE |
Altitude | msl bound lower : 5700 msl bound upper : 6000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : ixd |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | cruise other |
Route In Use | enroute airway : dov |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 13 flight time total : 210 flight time type : 100 |
ASRS Report | 202081 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude inflight encounter : weather non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera other other : unspecified cockpit |
Resolutory Action | flight crew : overcame equipment problem |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was heading southwest on V16 at 6000 ft with strong west crosswind (40 KTS) and strong up and downdrafts with mild chop. My #1 navcom apparently shook loose from its connection and I was not aware I had lost communication with approach. My #2 navcom was already tuned to patuxent river approach and VOR. I became aware that my #1 VOR was inoperative, while attempting to push it back into its mount I descended to 5700 ft and dover approach was trying to contact me. I also had drifted west of V16. After regaining #1 VOR I began a correction back to 6000 ft and V16 centerline. I was handed off to patuxent river approach but was informed I was still west of V16. I added further correction and regained proper orientation with V16. I was not aware of any conflict. When I first became aware of my inoperative navcom I should have switched my #2 navcom to dover approach and then correct #1. I also should have ensured that I didn't descend.
Original NASA ASRS Text
Title: SMA PLT HAS NAVCOM LOOSEN. LOST COM.
Narrative: I WAS HDG SW ON V16 AT 6000 FT WITH STRONG W XWIND (40 KTS) AND STRONG UP AND DOWNDRAFTS WITH MILD CHOP. MY #1 NAVCOM APPARENTLY SHOOK LOOSE FROM ITS CONNECTION AND I WAS NOT AWARE I HAD LOST COM WITH APCH. MY #2 NAVCOM WAS ALREADY TUNED TO PATUXENT RIVER APCH AND VOR. I BECAME AWARE THAT MY #1 VOR WAS INOP, WHILE ATTEMPTING TO PUSH IT BACK INTO ITS MOUNT I DSNDED TO 5700 FT AND DOVER APCH WAS TRYING TO CONTACT ME. I ALSO HAD DRIFTED W OF V16. AFTER REGAINING #1 VOR I BEGAN A CORRECTION BACK TO 6000 FT AND V16 CTRLINE. I WAS HANDED OFF TO PATUXENT RIVER APCH BUT WAS INFORMED I WAS STILL W OF V16. I ADDED FURTHER CORRECTION AND REGAINED PROPER ORIENTATION WITH V16. I WAS NOT AWARE OF ANY CONFLICT. WHEN I FIRST BECAME AWARE OF MY INOP NAVCOM I SHOULD HAVE SWITCHED MY #2 NAVCOM TO DOVER APCH AND THEN CORRECT #1. I ALSO SHOULD HAVE ENSURED THAT I DIDN'T DSND.
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.