37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1246864 |
Time | |
Date | 201503 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | VFR |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 70 Flight Crew Total 1900 Flight Crew Type 800 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 700 Vertical 700 |
Narrative:
During a VFR training flight; while using published right traffic pattern with 45 degree entry. Student & I made the standard self-announce calls at all prescribed locations (45; downwind; base & final. We heard and saw no other aircraft in the pattern until we were approximately 700 ft in altitude and 1/4 mile from touchdown on final approach to runway.a mooney aircraft suddenly appeared from behind; and on our left; overtaking us and turning in front of us; lining up for landing. As instructor; I took control of aircraft; made several calls to this aircraft and stated the traffic pattern for runway is right traffic. I received no response and I initiated a 'go-around' climbing and making an abrupt right turn evasive action to avoid potential collision.at the same time I heard another person on a ground portable radio advise; 'you guys nearly had a mid-air; I'll get his numbers.' my student and I departed the traffic pattern to the east and made a second VFR approach to an uneventful full stop landing. At the fuel pumps; when we landed; I saw the same mooney aircraft (with only one occupant; the pilot) shutting down to obtain fuel. The aero club chief flight instructor; (who had also witnessed this incident) was engaged in conversation with the pilot concerning his near fatal mistake.he later told me that the mooney had attempted to make a landing on runway 15 (wrong runway for current winds 310 degrees / 14g20 knots). When the mooney could not complete the landing he added some power; made a right 90 degree turn toward the west placing himself directly over the housing area at a low altitude and then made another turn; this time to the left approximately 270 degrees which placed him in direct collision course with me on short final to runway 33. During further discussion (which I also heard) he learned that the pilot was not on the proper CTAF frequency. He apparently thought the frequency was 122.9. The proper CTAF frequency is 122.725. During more conversation; he & I learned that the pilot had not done any pre-flight planning and therefore was not aware of the published right traffic pattern runway.in my opinion; the pilot of the mooney needs some refresher training and I recommend contact by FAA investigator to determine if his pilot skills and knowledge have deteriorated to a point; that he needs a complete retest.
Original NASA ASRS Text
Title: PA-28 Instructor pilot on short final is surprised by a M-20 overtaking from the left and landing ahead of him. A go around is initiated. After landing it was learned that the M20 pilot had attempted to land downwind on Runway 15 then went around; performing a 90/270 to come into conflict with the reporter. The wrong CTAF was also being used by the M20 pilot.
Narrative: During a VFR training flight; while using published Right Traffic pattern with 45 degree entry. Student & I made the standard self-announce calls at all prescribed locations (45; downwind; base & final. We heard and saw NO other aircraft in the pattern until we were approximately 700 Ft in altitude and 1/4 mile from touchdown on final approach to Runway.A Mooney aircraft suddenly appeared from behind; and on our left; overtaking us and turning in front of us; lining up for landing. As instructor; I took control of aircraft; made several calls to this aircraft and stated the traffic pattern for runway is RIGHT TRAFFIC. I received no response and I initiated a 'go-around' climbing and making an abrupt right turn evasive action to avoid potential collision.At the same time I heard another person on a ground portable radio advise; 'You guys nearly had a mid-air; I'll get his numbers.' My student and I departed the traffic pattern to the east and made a second VFR approach to an uneventful full stop landing. At the fuel pumps; when we landed; I saw the same Mooney aircraft (with only one occupant; the pilot) shutting down to obtain fuel. The Aero Club Chief Flight Instructor; (who had also witnessed this incident) was engaged in conversation with the pilot concerning his near fatal mistake.He later told me that the Mooney had attempted to make a landing on runway 15 (wrong runway for current winds 310 degrees / 14G20 Knots). When the Mooney could not complete the landing he added some power; made a RIGHT 90 degree turn toward the west placing himself directly over the housing area at a low altitude and then made another turn; this time to the left approximately 270 degrees which placed him in DIRECT collision course with me on short final to runway 33. During further discussion (which I also heard) He learned that the pilot was NOT on the proper CTAF frequency. He apparently thought the frequency was 122.9. The proper CTAF frequency is 122.725. During more conversation; he & I learned that the pilot had NOT done any pre-flight planning and therefore was not aware of the published right traffic pattern Runway.In my opinion; the pilot of the Mooney needs some refresher training and I recommend contact by FAA Investigator to determine if his pilot skills and knowledge have deteriorated to a point; that he needs a complete retest.
Data retrieved from NASA's ASRS site 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.