37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 497372 |
Time | |
Date | 200101 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : seg.airport |
State Reference | PA |
Altitude | msl single value : 3100 |
Environment | |
Flight Conditions | IMC |
Weather Elements | Snow |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mdt.tracon |
Operator | general aviation : personal |
Make Model Name | PA-23 Apache (& Geronimo Apache) |
Operating Under FAR Part | Part 91 |
Navigation In Use | other vortac |
Flight Phase | descent : intermediate altitude descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : multi engine pilot : instrument |
Experience | flight time last 90 days : 26 flight time total : 1050 flight time type : 200 |
ASRS Report | 497372 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : less severe inflight encounter : weather |
Independent Detector | aircraft equipment other aircraft equipment : vor/ils indicator prob. other flight crewa |
Resolutory Action | controller : provided flight assist flight crew : diverted to another airport other |
Consequence | other |
Supplementary | |
Problem Areas | Weather Aircraft |
Primary Problem | Aircraft |
Narrative:
While on an IFR flight plan, after descending to begin the vora approach on vector to final approach fix to seg, I became disoriented. The VOR needle seemed to first align with the course, but I was unable to hold course. After making several attempts to execute the approach, I abandoned the effort. I was then vectored to my designated alternate of mdt by harrisburg approach, but was unable to execute 2 ILS attempts to runway 13. Approach then vectored me toward the runway, where I was able to see approach lights, was cleared to land, and landed without further difficulty. I feel my disorientation was caused by an intermittent erratic VOR indication that I was not aware of, probably caused by a faulty VOR indicator or receiver problem. Earlier in the flight, I had communication difficulty with ZOB. There was a second hand-held transceiver in the aircraft during the flight, but it was not employed. Callback conversation with reporter revealed the following information: reporter stated that he did have the navigation received and VOR/ILS indicator checked out by maintenance, which found no noticeable problem. He further stated that he believed that he was too nervous and uncomfortable with the approachs which may have caused his erratic flight behavior rather than the equipment. He was also advised that when the ceiling/visibility is at least 800 ft, 2 mi, that other aircraft could be taxied across the runway to which he is headed causing trouble with the GS indications. He summarized his problem, by needing more instrument practice with a simulator and instructor.
Original NASA ASRS Text
Title: PLT OF A PIPER APACHE HAD TO REQUEST ATC ASSISTANCE FOR VECTORS TO THE RWY AFTER ATTEMPTING A VOR AND ILS APCH THAT COULD NOT BE MADE SUCCESSFULLY DUE TO THE ERRATIC MOVEMENT OF HIS COURSE INDICATOR.
Narrative: WHILE ON AN IFR FLT PLAN, AFTER DSNDING TO BEGIN THE VORA APCH ON VECTOR TO FINAL APCH FIX TO SEG, I BECAME DISORIENTED. THE VOR NEEDLE SEEMED TO FIRST ALIGN WITH THE COURSE, BUT I WAS UNABLE TO HOLD COURSE. AFTER MAKING SEVERAL ATTEMPTS TO EXECUTE THE APCH, I ABANDONED THE EFFORT. I WAS THEN VECTORED TO MY DESIGNATED ALTERNATE OF MDT BY HARRISBURG APCH, BUT WAS UNABLE TO EXECUTE 2 ILS ATTEMPTS TO RWY 13. APCH THEN VECTORED ME TOWARD THE RWY, WHERE I WAS ABLE TO SEE APCH LIGHTS, WAS CLRED TO LAND, AND LANDED WITHOUT FURTHER DIFFICULTY. I FEEL MY DISORIENTATION WAS CAUSED BY AN INTERMITTENT ERRATIC VOR INDICATION THAT I WAS NOT AWARE OF, PROBABLY CAUSED BY A FAULTY VOR INDICATOR OR RECEIVER PROB. EARLIER IN THE FLT, I HAD COM DIFFICULTY WITH ZOB. THERE WAS A SECOND HAND-HELD TRANSCEIVER IN THE ACFT DURING THE FLT, BUT IT WAS NOT EMPLOYED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE DID HAVE THE NAV RECEIVED AND VOR/ILS INDICATOR CHKED OUT BY MAINT, WHICH FOUND NO NOTICEABLE PROB. HE FURTHER STATED THAT HE BELIEVED THAT HE WAS TOO NERVOUS AND UNCOMFORTABLE WITH THE APCHS WHICH MAY HAVE CAUSED HIS ERRATIC FLT BEHAVIOR RATHER THAN THE EQUIP. HE WAS ALSO ADVISED THAT WHEN THE CEILING/VISIBILITY IS AT LEAST 800 FT, 2 MI, THAT OTHER ACFT COULD BE TAXIED ACROSS THE RWY TO WHICH HE IS HEADED CAUSING TROUBLE WITH THE GS INDICATIONS. HE SUMMARIZED HIS PROB, BY NEEDING MORE INST PRACTICE WITH A SIMULATOR AND INSTRUCTOR.
Data retrieved from NASA's ASRS site as of July 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.