37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1480669 |
Time | |
Date | 201709 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 10 Flight Crew Total 325 Flight Crew Type 325 |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Weather / Turbulence |
Narrative:
On IFR flight plan; smoke from forest fires caused hazy and poor visibility and was reliant on instruments for a good portion of the 3 hour flight. May have caused weariness at the end. Was at cruise altitude of 9000 and was given an amended IFR flight plan direct ZZZZZ1 and instructions to begin descent to 8000. Between zzzzz and ZZZZZ1 was given direct to filed destination ZZZ; a uncontrolled field with no instrument approaches available and given descent instructions. Smoke was now heavy and at times 0 visibility. Was cleared to 2500 and cleared to ZZZ. After reaching 2500 altitude; this is when I began having problems. For some reason; I wrongly assumed I could now go lower and begin looking for the airport. Still in IMC; began descent and eyes were too focused on looking for the airport or identifiable features that would lead me there. I had an improper instrument scan; if at all at this time and without realizing; was making a left turn heading toward higher terrain. Approach called to warn me that I had left the assigned altitude of 2500 and that I was off course and to immediately climb to assigned altitude. At this time I was well behind the airplane and my ascent and course were erratic and the controller sensed I was struggling a bit. He was amazing and I give all thanks to him for what could have turned into a worse situation if not for his help. I was so nervous I even accidentally kept my finger on the push to talk button. I was able to climb and assume course after the controllers help. After assigning a heading that would get me to some better visibility conditions; I spotted ZZZ runway and was able to cancel IFR and land in VFR conditions. After landing and reaching home; I called approach on the phone to thank them for their help; ask questions and to explain what was happening in this portion of the flight. I believe I was tired and stressed; being single pilot for 3 hours in IMC or close to it. Of course I never should have left the last assigned altitude and should have kept my scan until I reached VMC and not been looking out the window as much for the anticipated airport. All thanks go to a great team of controllers. I was able to actually speak on the phone with the person that helped me on the radio. I haven't had a lot of time in actual conditions over the last year; so my goal is to fly with an instructor on a regular basis in IMC. I did recently have an ipc which I have logged and am current instrument.
Original NASA ASRS Text
Title: PA28 pilot reported becoming disoriented during an IFR descent into an airport without an instrument approach.
Narrative: On IFR Flight plan; smoke from forest fires caused hazy and poor visibility and was reliant on instruments for a good portion of the 3 hour flight. May have caused weariness at the end. Was at cruise altitude of 9000 and was given an amended IFR flight plan direct ZZZZZ1 and instructions to begin descent to 8000. Between ZZZZZ and ZZZZZ1 was given direct to filed destination ZZZ; a uncontrolled field with no instrument approaches available and given descent instructions. Smoke was now heavy and at times 0 visibility. Was cleared to 2500 and cleared to ZZZ. After reaching 2500 altitude; this is when I began having problems. For some reason; I wrongly assumed I could now go lower and begin looking for the airport. Still in IMC; began descent and eyes were too focused on looking for the airport or identifiable features that would lead me there. I had an improper instrument scan; if at all at this time and without realizing; was making a left turn heading toward higher terrain. Approach called to warn me that I had left the assigned altitude of 2500 and that I was off course and to immediately climb to assigned altitude. At this time I was well behind the airplane and my ascent and course were erratic and the controller sensed I was struggling a bit. He was amazing and I give all thanks to him for what could have turned into a worse situation if not for his help. I was so nervous I even accidentally kept my finger on the push to talk button. I was able to climb and assume course after the controllers help. After assigning a heading that would get me to some better visibility conditions; I spotted ZZZ runway and was able to cancel IFR and land in VFR conditions. After landing and reaching home; I called Approach on the phone to thank them for their help; ask questions and to explain what was happening in this portion of the flight. I believe I was tired and stressed; being single pilot for 3 hours in IMC or close to it. Of course I never should have left the last assigned altitude and should have kept my scan until I reached VMC and not been looking out the window as much for the anticipated airport. All thanks go to a great team of controllers. I was able to actually speak on the phone with the person that helped me on the radio. I haven't had a lot of time in actual conditions over the last year; so my goal is to fly with an instructor on a regular basis in IMC. I did recently have an IPC which I have logged and am current instrument.
Data retrieved from NASA's ASRS site 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.