 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
General aviation pilot reported a go around due to a near mid air collision on short final.
| Attributes | |
| ACN | 1515676 |
| Time | |
| Date | 201802 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | RNM.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | VFR |
| Person 1 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Private |
| Experience | Flight Crew Last 90 Days 3 Flight Crew Total 388 Flight Crew Type 80 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC |
| Miss Distance | Horizontal 0 Vertical 100 |
Narrative:
Preparing for flight review with instructor. Flying touch and goes in pattern. Tower in operation. Cleared to land #1. Other traffic present in pattern but I was not instructed to follow any other traffic. On short final; I looked down and saw a cessna 172 almost directly beneath me. Applied full power and terminated the landing approach. Controller did not acknowledge conflict until after I had taken evasive action.the pattern was busy. There were aircraft arriving straight in; aircraft on practice instrument approaches (which means a GPS approach to [adjacent] runway with a circle to land - i.e. Opposite direction approach); multiple rotary wing aircraft as well as aircraft doing touch and go landings. Both right and left traffic was in use. The controller had given instructions to follow other aircraft in the landing sequence on other circuits in the pattern but did not identify other landing traffic on this occasion in my landing clearance.I do not know if this aircraft was straight-in traffic or if it was in the pattern. Both my instructor and I visually cleared the final course while on base. I do not know where the conflict aircraft was when we turned final - possibly already beneath us.it is my responsibility as pilot in command (PIC) to see and avoid and I did not see the conflict aircraft until the near miss. The controller had sequenced traffic and provided notification of other traffic in the pattern and the landing sequence which we were to follow up to this point. I am certain we did not disregard any instructions from the controller prior to this event. After the near-miss; the controller asked all traffic to report abeam the tower. This is a typical instruction when entering the pattern for landing. Perhaps the controller should routinely give this instruction for all circuits in the pattern when touch-and -go aircraft are present and the pattern is busy.
Original NASA ASRS Text
Title: General Aviation pilot reported a go around due to a near mid air collision on short final.
Narrative: Preparing for Flight Review with instructor. Flying touch and goes in pattern. Tower in operation. Cleared to land #1. Other traffic present in pattern but I was not instructed to follow any other traffic. On short final; I looked down and saw a Cessna 172 almost directly beneath me. Applied full power and terminated the landing approach. Controller did not acknowledge conflict until after I had taken evasive action.The pattern was busy. There were aircraft arriving straight in; aircraft on practice instrument approaches (which means a GPS approach to [adjacent] Runway with a circle to land - i.e. opposite direction approach); multiple rotary wing aircraft as well as aircraft doing touch and go landings. Both right and left traffic was in use. The controller had given instructions to follow other aircraft in the landing sequence on other circuits in the pattern but did not identify other landing traffic on this occasion in my landing clearance.I do not know if this aircraft was straight-in traffic or if it was in the pattern. Both my instructor and I visually cleared the final course while on base. I do not know where the conflict aircraft was when we turned final - possibly already beneath us.It is my responsibility as Pilot in Command (PIC) to see and avoid and I did not see the conflict aircraft until the near miss. The controller had sequenced traffic and provided notification of other traffic in the pattern and the landing sequence which we were to follow up to this point. I am certain we did not disregard any instructions from the controller prior to this event. After the near-miss; the controller asked all traffic to report abeam the tower. This is a typical instruction when entering the pattern for landing. Perhaps the controller should routinely give this instruction for all circuits in the pattern when touch-and -go aircraft are present and the pattern is busy.
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.