![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 118704 |
| Time | |
| Date | 198907 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : guu |
| State Reference | IN |
| Altitude | agl bound lower : 700 agl bound upper : 700 |
| Environment | |
| Flight Conditions | IMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | tower : guu |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
| Flight Phase | cruise other descent : approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | climbout : takeoff cruise other |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 20 flight time total : 380 flight time type : 12 |
| ASRS Report | 118704 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | conflict : nmac non adherence : clearance |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : became reoriented flight crew : took evasive action |
| Consequence | Other |
| Miss Distance | horizontal : 3000 vertical : 400 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
First let me describe the reason the incident occurred. The main reason is due to confusion of communication, which was mainly due to radio problems I have having at the time. Now I'll describe the situations and events that took place. I was on the localizer approach to runway 30, because my glide slope and marker beacons had gone out. Also, my communication radios were garbled. I was cleared to land on runway 2, which I do remember. However, in the confusion of trying to get my radios working, I thought I was cleared to enter a left downwind for runway 20. I reported turning final for runway 20. The tower said they didn't have me in sight and that is when I realized I was still supposed to be on approach for runway 2. Another aircraft was departing runway 2. However, as soon as I reported where I was, we both turned to the right, which was in effect, evasive action. In my opinion, there was never any imminent danger. A human factor which was in play at the time was my being nervous, because I was loosing my radios and it was instrument conditions.
Original NASA ASRS Text
Title: NMAC OCCURRED WHEN SMA CIRCLED TO WRONG RWY AFTER CONDUCTING LOC APCH.
Narrative: FIRST LET ME DESCRIBE THE REASON THE INCIDENT OCCURRED. THE MAIN REASON IS DUE TO CONFUSION OF COMMUNICATION, WHICH WAS MAINLY DUE TO RADIO PROBLEMS I HAVE HAVING AT THE TIME. NOW I'LL DESCRIBE THE SITUATIONS AND EVENTS THAT TOOK PLACE. I WAS ON THE LOC APCH TO RWY 30, BECAUSE MY GLIDE SLOPE AND MARKER BEACONS HAD GONE OUT. ALSO, MY COMMUNICATION RADIOS WERE GARBLED. I WAS CLRED TO LAND ON RWY 2, WHICH I DO REMEMBER. HOWEVER, IN THE CONFUSION OF TRYING TO GET MY RADIOS WORKING, I THOUGHT I WAS CLRED TO ENTER A LEFT DOWNWIND FOR RWY 20. I REPORTED TURNING FINAL FOR RWY 20. THE TWR SAID THEY DIDN'T HAVE ME IN SIGHT AND THAT IS WHEN I REALIZED I WAS STILL SUPPOSED TO BE ON APCH FOR RWY 2. ANOTHER ACFT WAS DEPARTING RWY 2. HOWEVER, AS SOON AS I REPORTED WHERE I WAS, WE BOTH TURNED TO THE RIGHT, WHICH WAS IN EFFECT, EVASIVE ACTION. IN MY OPINION, THERE WAS NEVER ANY IMMINENT DANGER. A HUMAN FACTOR WHICH WAS IN PLAY AT THE TIME WAS MY BEING NERVOUS, BECAUSE I WAS LOOSING MY RADIOS AND IT WAS INSTRUMENT CONDITIONS.
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.