37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1465137 |
Time | |
Date | 201707 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | OWD.Airport |
State Reference | MA |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 270 Flight Crew Type 20 |
Events | |
Anomaly | Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Weather / Turbulence |
Narrative:
During approach in to owd; I was in IMC being vectored to final at 2000 feet. Once cleared for the GPS 35 approach; I began my descent along the glideslope to the FAF which was cupug at 1700 feet. The rain was sufficiently heavy that it was impacting my static ports. I was seeing sudden swings in vertical speed and substantial variations in indicated altitude that slowly returned to normal; but I remained on/near glideslope as indicated by the lpv guidance. Due to the turbulence and rain; it was a high workload situation. Not far beyond the FAF; owd reported a low altitude alert. I reported that my altimeter setting was correct and that I was on the GPS glide path. I was one dot low on the lpv glide slope. At about this time I also had visual ground contact. This was consistent with PIREP from a previously arriving aircraft observing ceilings at 1700 feet. I struggled to maintain a stable descent rate as I continued the approach and remained low on the glideslope but on-scale. The tower issued two more low altitude alerts; presumably because my varying descent rate was causing a predicted insufficient altitude combined with being a little low on the glideslope. With each low altitude alert; I added some power and back pressure on the yoke; which I needed to do anyway to bring the glideslope needle back down. I didn't note the exact altitude I had the runway in sight but it took me a few moments due to lack of familiarity with the area. I would estimate 600-800 feet AGL. The PAPI was indicating 3 red so I leveled out to get 2 white and two red and continued to a normal landing. The aircraft's GPS provides forward looking terrain alerts and none were received during the approach.a lesson learned from this is that I should consider alternate airports if the rain is heavy enough to affect instruments or considered use of the alternate static source. I should have more seriously considered going missed upon receiving follow up low altitude alerts. My logic was that as long as I had the lpv glideslope I was protected; but if I desensitize myself to that useful tool then I may not help me in a situation in which I made a mistake in setting up or interpreting the approach.
Original NASA ASRS Text
Title: GA pilot reported receiving several low altitude alerts on the GPS 35 approach to OWD during heavy rain.
Narrative: During approach in to OWD; I was in IMC being vectored to final at 2000 feet. Once cleared for the GPS 35 approach; I began my descent along the glideslope to the FAF which was CUPUG at 1700 feet. The rain was sufficiently heavy that it was impacting my static ports. I was seeing sudden swings in vertical speed and substantial variations in indicated altitude that slowly returned to normal; but I remained on/near glideslope as indicated by the LPV guidance. Due to the turbulence and rain; it was a high workload situation. Not far beyond the FAF; OWD reported a low altitude alert. I reported that my altimeter setting was correct and that I was on the GPS glide path. I was one dot low on the LPV glide slope. At about this time I also had visual ground contact. This was consistent with PIREP from a previously arriving aircraft observing ceilings at 1700 feet. I struggled to maintain a stable descent rate as I continued the approach and remained low on the glideslope but on-scale. The Tower issued two more low altitude alerts; presumably because my varying descent rate was causing a predicted insufficient altitude combined with being a little low on the glideslope. With each low altitude alert; I added some power and back pressure on the yoke; which I needed to do anyway to bring the glideslope needle back down. I didn't note the exact altitude I had the runway in sight but it took me a few moments due to lack of familiarity with the area. I would estimate 600-800 feet AGL. The PAPI was indicating 3 red so I leveled out to get 2 white and two red and continued to a normal landing. The aircraft's GPS provides forward looking terrain alerts and none were received during the approach.A lesson learned from this is that I should consider alternate airports if the rain is heavy enough to affect instruments or considered use of the alternate static source. I should have more seriously considered going missed upon receiving follow up low altitude alerts. My logic was that as long as I had the LPV glideslope I was protected; but if I desensitize myself to that useful tool then I may not help me in a situation in which I made a mistake in setting up or interpreting the approach.
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.