37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1202400 |
Time | |
Date | 201409 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZME.ARTCC |
State Reference | TN |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Flight Phase | Final Approach Initial Approach |
Route In Use | Other Instrument Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 27 |
Events | |
Anomaly | Conflict NMAC |
Narrative:
I was in the process of taking over the sector. During my briefing; I heard aircraft X cancel his IFR clearance into hot. Aircraft Y was holding at hossy waiting his turn for a practice approach to hot. The controller that I was relieving cleared aircraft Y for an ILS approach to hot. I took over the sector; and one of the first things I did was switch aircraft Y to advisory frequency at hot and ask the pilot to report his missed approach. A few minutes later aircraft Y reported his missed approach. At the same time aircraft X came back on my frequency to report that some aircraft had gotten very close to his aircraft while he was landing. I asked aircraft X if he was reporting a near miss; and he said he was doing just that. I made sure that aircraft X was safely on the ground; and then I reported the incident to management at memphis ARTCC.I would make double sure that both pilots were aware of each other. In this case the second pilot knew about the first aircraft. There may have been a third aircraft out there that none of us knew about. The pilot of aircraft X did not positively identify the other aircraft.
Original NASA ASRS Text
Title: ZME Controller describes an NMAC where Aircraft X cancels IFR and goes VFR; and then Aircraft Y is cleared for an ILS Approach to the same airport. Aircraft Y cancels IFR and Aircraft X comes back on frequency reporting a near miss. Controller is unsure of the other aircraft involved in the near miss since Aircraft X does not identify it.
Narrative: I was in the process of taking over the sector. During my briefing; I heard Aircraft X cancel his IFR clearance into HOT. Aircraft Y was holding at HOSSY waiting his turn for a practice approach to HOT. The controller that I was relieving cleared Aircraft Y for an ILS approach to HOT. I took over the sector; and one of the first things I did was switch Aircraft Y to advisory frequency at HOT and ask the pilot to report his missed approach. A few minutes later Aircraft Y reported his missed approach. At the same time Aircraft X came back on my frequency to report that some aircraft had gotten very close to his aircraft while he was landing. I asked Aircraft X if he was reporting a near miss; and he said he was doing just that. I made sure that Aircraft X was safely on the ground; and then I reported the incident to management at Memphis ARTCC.I would make double sure that both pilots were aware of each other. In this case the second pilot knew about the first aircraft. There may have been a third aircraft out there that none of us knew about. The pilot of Aircraft X did not positively identify the other aircraft.
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.