M20 pilot reports conflicting glideslope information during ILS 30 approach at jef and breaks out at...

Attributes
ACN	990764
Time
Date	201201
Local Time Of Day	0601-1200
Place
Locale Reference	JEF.Airport
State Reference	MO
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Make Model Name	M-20 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Commercial Flight Crew Instrument
Experience	Flight Crew Last 90 Days 25 Flight Crew Total 5500 Flight Crew Type 60
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural FAR Deviation - Procedural Clearance Inflight Event / Encounter Weather / Turbulence

Narrative:

[I was] flying ILS approach to runway 30 at jef vectored to final ahead of a faster aircraft. [I] attempted to fly approach at faster than standard airspeed; causing everything to occur quicker than normal. Was receiving conflicting readings from the glideslope on two different CDI's; did not see this until late in the approach due to intercept from above published altitudes. GPS and altitude verified the correct CDI data; distraction was associated with the data conflict; arrived at target altitude and broke out of clouds just beyond threshold; decided to maneuver to complete landing when at minimums upon the breakout from clouds. Result was non-standard landing maneuvers; instead of the cleared straight in approach. Approach to low IFR airport was at end of a 2:20 minute IFR flight in IMC and weather avoidance. Correct decision would have been to execute missed approach and trouble shoot any problems at altitude; then re-fly approach.

Original NASA ASRS Text

Title: M20 pilot reports conflicting glideslope information during ILS 30 approach at JEF and breaks out at 300 FT over the threshold. Non-standard landing maneuvers were used to complete landing when at minimums; that did not comply with straight in landing clearance.

Narrative: [I was] flying ILS approach to Runway 30 at JEF vectored to final ahead of a faster aircraft. [I] attempted to fly approach at faster than standard airspeed; causing everything to occur quicker than normal. Was receiving conflicting readings from the glideslope on two different CDI's; did not see this until late in the approach due to intercept from above published altitudes. GPS and altitude verified the correct CDI data; distraction was associated with the data conflict; arrived at target altitude and broke out of clouds just beyond threshold; decided to maneuver to complete landing when at minimums upon the breakout from clouds. Result was non-standard landing maneuvers; instead of the cleared straight in approach. Approach to low IFR airport was at end of a 2:20 MINUTE IFR flight in IMC and weather avoidance. Correct decision would have been to execute missed approach and trouble shoot any problems at altitude; then re-fly approach.

Data retrieved from NASA's ASRS site as of July 2013 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.

M20 pilot reports conflicting glideslope information during ILS 30 approach at jef and breaks out at 300 ft over the threshold. Non-standard landing maneuvers were used to complete landing when at minimums; that did not comply with straight in landing clearance.