![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 101024 |
| Time | |
| Date | 198812 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : jvl |
| State Reference | IL |
| Altitude | msl bound lower : 2700 msl bound upper : 2700 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : rfd |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
| Navigation In Use | ils localizer & glide slope : jvl |
| Flight Phase | descent : approach |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 32 flight time total : 2330 flight time type : 35 |
| ASRS Report | 101024 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Events | |
| Anomaly | aircraft equipment problem : critical other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Ambiguous |
| Air Traffic Incident | other |
| Situations | |
| Navigational Aid | Unspecified |
Narrative:
After being aligned with the ILS the controller had to give me a go around. Aircraft ahead of me was having problems and declared a missed approach. After vectoring I was cleared for the approach and given the tower frequency. After intercepting the G/south the localizer needle began to drift to the right--correcting for the drift did not help. As I was almost to call a missed approach I broke out of IMC much to the right of the normal approach path. I called the tower and was cleared to land. Later I made an ILS approach at another ILS in VFR WX and found my aircraft equipment working normally. I find the jvl ILS is not up to full operating power. Callback conversation with reporter revealed the following: reporter said he did not report the ILS problem to the FAA because he thought it was a problem with his equipment. Later during the day he shot another ILS at another airport in VMC and he said his equipment was fine. He therefore thinks it was a NAVAID problem.
Original NASA ASRS Text
Title: ILS INDICATIONS CAUSE REPORTER TO BREAK OUT OF OVERCAST OFF COURSE. REPORTER BELIEVES PROBLEM WAS WITH ILS SIGNAL.
Narrative: AFTER BEING ALIGNED WITH THE ILS THE CTLR HAD TO GIVE ME A GAR. ACFT AHEAD OF ME WAS HAVING PROBS AND DECLARED A MISSED APCH. AFTER VECTORING I WAS CLRED FOR THE APCH AND GIVEN THE TWR FREQ. AFTER INTERCEPTING THE G/S THE LOC NEEDLE BEGAN TO DRIFT TO THE RIGHT--CORRECTING FOR THE DRIFT DID NOT HELP. AS I WAS ALMOST TO CALL A MISSED APCH I BROKE OUT OF IMC MUCH TO THE RIGHT OF THE NORMAL APCH PATH. I CALLED THE TWR AND WAS CLRED TO LAND. LATER I MADE AN ILS APCH AT ANOTHER ILS IN VFR WX AND FOUND MY ACFT EQUIP WORKING NORMALLY. I FIND THE JVL ILS IS NOT UP TO FULL OPERATING PWR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR SAID HE DID NOT RPT THE ILS PROB TO THE FAA BECAUSE HE THOUGHT IT WAS A PROB WITH HIS EQUIP. LATER DURING THE DAY HE SHOT ANOTHER ILS AT ANOTHER ARPT IN VMC AND HE SAID HIS EQUIP WAS FINE. HE THEREFORE THINKS IT WAS A NAVAID PROB.
Data retrieved from NASA's ASRS site as of August 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.