 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
PA34-200 pilot has near midair collision with mooney 201 in non tower airport approach landing. Second aircraft not using radio for position reports.
| Attributes | |
| ACN | 374752 |
| Time | |
| Date | 199707 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : 81b |
| State Reference | ME |
| Altitude | msl bound lower : 1400 msl bound upper : 1400 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : luk |
| Operator | general aviation : personal |
| Make Model Name | PA-34-200T Turbo Seneca II |
| Operating Under FAR Part | Part 91 |
| Flight Phase | other |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | M-20 J (201) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach other |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : flight engineer pilot : commercial pilot : cfi pilot : atp pilot : instrument |
| Experience | flight time last 90 days : 200 flight time total : 9000 flight time type : 300 |
| ASRS Report | 374752 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private |
| Events | |
| Anomaly | conflict : nmac other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 50 vertical : 100 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft #1 entered the pattern at oxford airport, me, and called the entry on 122.8 (CTAF). Aircraft #1 called downwind leg and base leg. Aircraft #1 did not see other aircraft or hear any xmissions during or after pattern entry from other aircraft in the oxford pattern. After turning a base leg and calling a base, aircraft #2 was observed above and to the right of aircraft #1. Aircraft #1 initiated evasive action descending in a shallow left turn. Aircraft #2 initiated evasive action climbing to the right. Prevention: 1) listen to and use radio for pattern work. 2) use standard pattern entry. 3) keep eyes outside. Callback conversation with reporter revealed the following information: reporter states he tried to speak with the other pilot in a non accusatory manner but the mooney pilot was just too busy and would not take the time to communicate. He did not seem to be very concerned about the proximity of the aircraft. Airport personnel told reporter that this pilot is an ongoing problem because he does not listen to the radio, he does not talk on the radio and he does not use a standard pattern. He apparently flies direct with GPS and angles to the runway for straight-in approach, no pattern procedures whatsoever. Reporter is a former military fighter pilot and said he has never been so close to another aircraft without knowing of its presence. He recreated the incident on his computer simulator at home and determined that the mooney pilot was well above him on a high speed descent and positioned so that reporter was looking into the sun. This may be why the reporter was unable to sight the mooney any earlier. After discussion with people at the airport it was recommended that he contact the pdx FAA to see if they would talk to the other pilot. An FAA representative did so and gave the mooney pilot a good idea of why it is important for others to know where he is and what he intends to do. Reporter is an air carrier pilot and has ordered a TCASII for his aircraft hoping he can avoid such an incident in the future.
Original NASA ASRS Text
Title: PA34-200 PLT HAS NMAC WITH MOONEY 201 IN NON TWR ARPT APCH LNDG. SECOND ACFT NOT USING RADIO FOR POS RPTS.
Narrative: ACFT #1 ENTERED THE PATTERN AT OXFORD ARPT, ME, AND CALLED THE ENTRY ON 122.8 (CTAF). ACFT #1 CALLED DOWNWIND LEG AND BASE LEG. ACFT #1 DID NOT SEE OTHER ACFT OR HEAR ANY XMISSIONS DURING OR AFTER PATTERN ENTRY FROM OTHER ACFT IN THE OXFORD PATTERN. AFTER TURNING A BASE LEG AND CALLING A BASE, ACFT #2 WAS OBSERVED ABOVE AND TO THE R OF ACFT #1. ACFT #1 INITIATED EVASIVE ACTION DSNDING IN A SHALLOW L TURN. ACFT #2 INITIATED EVASIVE ACTION CLBING TO THE R. PREVENTION: 1) LISTEN TO AND USE RADIO FOR PATTERN WORK. 2) USE STANDARD PATTERN ENTRY. 3) KEEP EYES OUTSIDE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES HE TRIED TO SPEAK WITH THE OTHER PLT IN A NON ACCUSATORY MANNER BUT THE MOONEY PLT WAS JUST TOO BUSY AND WOULD NOT TAKE THE TIME TO COMMUNICATE. HE DID NOT SEEM TO BE VERY CONCERNED ABOUT THE PROX OF THE ACFT. ARPT PERSONNEL TOLD RPTR THAT THIS PLT IS AN ONGOING PROB BECAUSE HE DOES NOT LISTEN TO THE RADIO, HE DOES NOT TALK ON THE RADIO AND HE DOES NOT USE A STANDARD PATTERN. HE APPARENTLY FLIES DIRECT WITH GPS AND ANGLES TO THE RWY FOR STRAIGHT-IN APCH, NO PATTERN PROCS WHATSOEVER. RPTR IS A FORMER MIL FIGHTER PLT AND SAID HE HAS NEVER BEEN SO CLOSE TO ANOTHER ACFT WITHOUT KNOWING OF ITS PRESENCE. HE RECREATED THE INCIDENT ON HIS COMPUTER SIMULATOR AT HOME AND DETERMINED THAT THE MOONEY PLT WAS WELL ABOVE HIM ON A HIGH SPD DSCNT AND POSITIONED SO THAT RPTR WAS LOOKING INTO THE SUN. THIS MAY BE WHY THE RPTR WAS UNABLE TO SIGHT THE MOONEY ANY EARLIER. AFTER DISCUSSION WITH PEOPLE AT THE ARPT IT WAS RECOMMENDED THAT HE CONTACT THE PDX FAA TO SEE IF THEY WOULD TALK TO THE OTHER PLT. AN FAA REPRESENTATIVE DID SO AND GAVE THE MOONEY PLT A GOOD IDEA OF WHY IT IS IMPORTANT FOR OTHERS TO KNOW WHERE HE IS AND WHAT HE INTENDS TO DO. RPTR IS AN ACR PLT AND HAS ORDERED A TCASII FOR HIS ACFT HOPING HE CAN AVOID SUCH AN INCIDENT IN THE FUTURE.
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.