 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A C182 conducting in-flight ILS GS maintenance troubleshooting; had near midair collision with a piper arrow on the same GS.
| Attributes | |
| ACN | 653741 |
| Time | |
| Date | 200504 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | intersection : catch |
| State Reference | IN |
| Altitude | msl single value : 2500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : sdf.tracon |
| Operator | Other |
| Make Model Name | Skylane 182/RG Turbo Skylane/RG |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | ils localizer & glide slope : 18 |
| Flight Phase | descent : approach |
| Flight Plan | None |
| Aircraft 2 | |
| Controlling Facilities | tracon : sdf.tracon |
| Make Model Name | PA-28 Cherokee Arrow IV |
| Flight Phase | descent : approach |
| Person 1 | |
| Affiliation | company : air carrier government other |
| Function | observation : observer |
| Qualification | pilot : cfi pilot : atp pilot : multi engine |
| Experience | flight time last 90 days : 15 flight time total : 5300 flight time type : 100 |
| ASRS Report | 653741 |
| Person 2 | |
| Affiliation | government other |
| Events | |
| Anomaly | aircraft equipment problem : less severe conflict : nmac non adherence : far non adherence : published procedure other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took precautionary avoidance action flight crew : took evasive action |
| Consequence | Other |
| Miss Distance | horizontal : 50 vertical : 20 |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Aircraft |
| Primary Problem | Flight Crew Human Performance |
Narrative:
We were checking for a buzzing sound that maintenance was not able to find. It was found (believed to be rigging problem in cowl flap) and conditions to duplicate were documented. There had also been a report that the GS was inoperative in the aircraft. When we finished documenting the buzzing sound; we were about 3 NM northeast of catch. We decided to check to see if we could receive the GS and get a determination. We intercepted the localizer but got no needle movement we were underneath the glide path and maintained altitude to see if it would come in. Just as we were coming over catch; I saw the other aircraft descending and appearing to slow. I had been monitoring approach frequency and jvy CTAF but had heard nothing in our area. After I maneuvered down and to the left; the other aircraft called 'over catch inbound on the ILS runway 18 clark county.' I called and said we were over catch also and that we had had an near midair collision. He called back 'sorry' and continued on. I then realized that I was broadcasting on louisville approach but was listening to him on CTAF. In the future; for higher safety; I will get flight following for any time I am in the vicinity of an approach. This should help with the traffic and with helping to make sure I'm on the right frequency. I had felt that just monitoring approach would help me to avoid other aircraft in busy airspace. It never occurred to me what the consequences of another aircraft doing the same thing were. The near midair collision was a classic low wing descending onto a high wing.
Original NASA ASRS Text
Title: A C182 CONDUCTING INFLT ILS GS MAINT TROUBLESHOOTING; HAD NMAC WITH A PIPER ARROW ON THE SAME GS.
Narrative: WE WERE CHKING FOR A BUZZING SOUND THAT MAINT WAS NOT ABLE TO FIND. IT WAS FOUND (BELIEVED TO BE RIGGING PROB IN COWL FLAP) AND CONDITIONS TO DUPLICATE WERE DOCUMENTED. THERE HAD ALSO BEEN A RPT THAT THE GS WAS INOP IN THE ACFT. WHEN WE FINISHED DOCUMENTING THE BUZZING SOUND; WE WERE ABOUT 3 NM NE OF CATCH. WE DECIDED TO CHK TO SEE IF WE COULD RECEIVE THE GS AND GET A DETERMINATION. WE INTERCEPTED THE LOC BUT GOT NO NEEDLE MOVEMENT WE WERE UNDERNEATH THE GLIDE PATH AND MAINTAINED ALT TO SEE IF IT WOULD COME IN. JUST AS WE WERE COMING OVER CATCH; I SAW THE OTHER ACFT DSNDING AND APPEARING TO SLOW. I HAD BEEN MONITORING APCH FREQ AND JVY CTAF BUT HAD HEARD NOTHING IN OUR AREA. AFTER I MANEUVERED DOWN AND TO THE L; THE OTHER ACFT CALLED 'OVER CATCH INBOUND ON THE ILS RWY 18 CLARK COUNTY.' I CALLED AND SAID WE WERE OVER CATCH ALSO AND THAT WE HAD HAD AN NMAC. HE CALLED BACK 'SORRY' AND CONTINUED ON. I THEN REALIZED THAT I WAS BROADCASTING ON LOUISVILLE APCH BUT WAS LISTENING TO HIM ON CTAF. IN THE FUTURE; FOR HIGHER SAFETY; I WILL GET FLT FOLLOWING FOR ANY TIME I AM IN THE VICINITY OF AN APCH. THIS SHOULD HELP WITH THE TFC AND WITH HELPING TO MAKE SURE I'M ON THE RIGHT FREQ. I HAD FELT THAT JUST MONITORING APCH WOULD HELP ME TO AVOID OTHER ACFT IN BUSY AIRSPACE. IT NEVER OCCURRED TO ME WHAT THE CONSEQUENCES OF ANOTHER ACFT DOING THE SAME THING WERE. THE NMAC WAS A CLASSIC LOW WING DSNDING ONTO A HIGH WING.
Data retrieved from NASA's ASRS site as of January 2009 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.