 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
SR22 pilot reported completing the final 18 miles to destination VFR under a cloud layer at less than 800 feet above hills and obstructions.
| Attributes | |
| ACN | 1517123 |
| Time | |
| Date | 201802 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 10 Flight Crew Total 4800 Flight Crew Type 120 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Weather / Turbulence |
Narrative:
I filed an IFR flight. It was clear/VFR [at departure airport] and 1;000-1;200 ovc at destination. I was aware the approaches [at destination] are 'na at night'; however; my ETA was within 15 minutes of sunset; which was not end of civil twilight; nor one hour after sunset. So; I was surprised I wasn't able to get the approach. Interestingly; the clear skies turned into a solid overcast layer within the last 20 miles to my destination. So; I was contemplating shooting an approach at ZZZ1 or ZZZ2 and continuing to [destination] VFR; respecting the cloud clearance requirements.with ATC TRACON coordinating and considering what they could offer (which was taking time); I quickly said 'nxxxxx would like to cancel IFR.' the controller seemed a little confused and/or concerned but I replied I could get under the cloud deck visually and remain VFR for the remaining ~18 miles. He told me to continue VFR as requested but remain on my current transponder code.I continued visually into class G airspace (approximately 800 feet AGL) for the remainder until I saw the airport beacon and flew a relatively standard traffic pattern.as I reflected on my flight I grew alarmed at the decision I made; as I feel safety may have been unintentionally compromised. Here is why:as I was flying the last 18 miles to destination under the clouds; I expected the clouds to be no lower than 1000-1200 feet with no problems flying around 2200 MSL or 800 AGL for that final segment. However; I was then reminded of numerous rolling hills and tower obstructions. In fact; there was a momentary aural alert of 'terrain; terrain' due to my lower than planned AGL altitude as I passed around hills/obstructions. This was uncomfortable at the time but seemed like a controlled situation. When I reflect back and look at my online flight track; I do not feel I made the conservative decision; especially at dusk. I believe I was pressured to get to my destination and not divert; and I should have considered the 'connecting chain-links.'
Original NASA ASRS Text
Title: SR22 pilot reported completing the final 18 miles to destination VFR under a cloud layer at less than 800 feet above hills and obstructions.
Narrative: I filed an IFR flight. It was clear/VFR [at departure airport] and 1;000-1;200 OVC at destination. I was aware the approaches [at destination] are 'NA at Night'; however; my ETA was within 15 minutes of sunset; which was not end of civil twilight; nor one hour after sunset. So; I was surprised I wasn't able to get the approach. Interestingly; the clear skies turned into a solid overcast layer within the last 20 miles to my destination. So; I was contemplating shooting an approach at ZZZ1 or ZZZ2 and continuing to [destination] VFR; respecting the cloud clearance requirements.With ATC TRACON coordinating and considering what they could offer (which was taking time); I quickly said 'Nxxxxx would like to cancel IFR.' The controller seemed a little confused and/or concerned but I replied I could get under the cloud deck visually and remain VFR for the remaining ~18 miles. He told me to continue VFR as requested but remain on my current transponder code.I continued visually into class G airspace (approximately 800 feet AGL) for the remainder until I saw the airport beacon and flew a relatively standard traffic pattern.As I reflected on my flight I grew alarmed at the decision I made; as I feel safety may have been unintentionally compromised. Here is why:As I was flying the last 18 miles to destination under the clouds; I expected the clouds to be no lower than 1000-1200 feet with no problems flying around 2200 MSL or 800 AGL for that final segment. However; I was then reminded of numerous rolling hills and tower obstructions. In fact; there was a momentary aural alert of 'terrain; terrain' due to my lower than planned AGL altitude as I passed around hills/obstructions. This was uncomfortable at the time but seemed like a controlled situation. When I reflect back and look at my online flight track; I do not feel I made the conservative decision; especially at dusk. I believe I was pressured to get to my destination and not divert; and I should have considered the 'connecting chain-links.'
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.