 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
GA pilot reported an inoperative transponder and busy ATC situation resulted in a near midair collision while on approach.
| Attributes | |
| ACN | 1624742 |
| Time | |
| Date | 201902 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | PHF.Airport |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Component | |
| Aircraft Component | Transponder |
| Person 1 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Commercial |
| Experience | Flight Crew Last 90 Days 15 Flight Crew Total 1020 Flight Crew Type 600 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Airspace Violation All Types Conflict NMAC Deviation - Procedural Clearance |
Narrative:
Contacted norfolk approach to request GPS rwy 2 approach to phf on instrument currency/practice flight with cfii. Approach provided a transponder code and we began [the] approach but approach was busy and never confirmed radar contact. I; the pilot in command; asked if I should continue but cfii seemed unconcerned so PIC continued approach. Finally upon another request to approach; orf approach requested we ident as approach had previously done but could not see us on radar. Did not see transponder interrogation and assumed transponder inoperative tower requested we do 360's to avoid incoming traffic when we saw and reported other traffic on approach to runway 7 and warned us. Upon landing at home field the avionics shop determined transponder inoperative and repaired. Lesson learned! Approach control did not handle us appropriately due to busyness of other traffic; requesting we contact tower without indicating an inoperative transponder to us; resulting in a potential near mid-air with a aircraft Y on approach to runway 7. Phf tower gave us warning to not enter airspace without approval that I believed was already granted.
Original NASA ASRS Text
Title: GA pilot reported an inoperative transponder and busy ATC situation resulted in a near midair collision while on approach.
Narrative: Contacted Norfolk Approach to request GPS Rwy 2 approach to PHF on instrument currency/practice flight with CFII. Approach provided a transponder code and we began [the] approach but Approach was busy and never confirmed radar contact. I; the pilot in command; asked if I should continue but CFII seemed unconcerned so PIC continued approach. Finally upon another request to approach; ORF Approach requested we ident as approach had previously done but could not see us on radar. Did not see transponder interrogation and assumed transponder inoperative Tower requested we do 360's to avoid incoming traffic when we saw and reported other traffic on approach to Runway 7 and warned us. Upon landing at home field the avionics shop determined transponder inoperative and repaired. Lesson learned! Approach Control did not handle us appropriately due to busyness of other traffic; requesting we contact Tower without indicating an inoperative transponder to us; resulting in a potential near mid-air with a Aircraft Y on approach to RWY 7. PHF Tower gave us warning to not enter airspace without approval that I believed was already granted.
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.