 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Roa TRACON controller reported airborne conflict between two aircraft; after being distracted by a third aircraft that was VFR in IMC.
| Attributes | |
| ACN | 1581737 |
| Time | |
| Date | 201809 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ROA.TRACON |
| State Reference | VA |
| Environment | |
| Flight Conditions | Marginal |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Transport Low Wing 2 Turbojet Eng |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural FAR Inflight Event / Encounter VFR In IMC Inflight Event / Encounter CFTT / CFIT |
Narrative:
Normal east radar position; weather was reported 10SM OVC012. Aircraft Z departed runway 34; VFR; to the north east practice area. Aircraft X was on final for ILS 34 from the south. Aircraft Y was in the departure list for runway 34 with a west turnout. Aircraft Z got around 2 miles northeast of the field and encountered clouds and lost site of the surrounding mountains. I informed him he was around 100 feet above the mountain in question and asked his intentions; followed by asking him if he wanted [additional services] and he did. He seemed very spooked and said his passenger was as well. I saw him starting to turn towards the field and thought he could possibly descend rapidly back to the field. I told tower of the [situation] and as a precaution I told them to break him off the approach on a 270; thinking aircraft Z was going to head straight at the airport that wasn't insight.the loss of separation comes from the 270 turn off final for aircraft X and the departure of aircraft Y on a 250 heading off of runway 34. I initially thought I had enough lateral separation; then realized it was going to be closer than I assumed and when I saw it; not long after; turned both away from each other. I believe the lateral separation was 2.6 NM. After aircraft Z [notified us]; I asked him what he wanted to do. I suggested a possible IFR pickup for radar vectors back to roa for the ILS 34. He said an IFR pickup sounds like the best. I followed it by clearing him; since he was still climbing and was above the MVA in the area. It was when I tried to turn him final to join the approach he informed me that he wasn't IFR rated. We followed by giving him a vector to maintain until we found an airport with suitable VMC. I was unaware of specific phraseology in an IFR pickup; and thought suggesting IFR for an approach--with his agreement; meant he was qualified. I'm unaware that you can't suggest IFR like a SVFR to an aircraft.no recommendations; just reviewed 7110 chapter 10 on VFR aircraft encountering bad weather.
Original NASA ASRS Text
Title: ROA TRACON Controller reported airborne conflict between two aircraft; after being distracted by a third aircraft that was VFR in IMC.
Narrative: Normal East Radar position; weather was reported 10SM OVC012. Aircraft Z departed Runway 34; VFR; to the North East Practice Area. Aircraft X was on final for ILS 34 from the south. Aircraft Y was in the departure list for Runway 34 with a west turnout. Aircraft Z got around 2 miles northeast of the field and encountered clouds and lost site of the surrounding mountains. I informed him he was around 100 feet above the mountain in question and asked his intentions; followed by asking him if he wanted [additional services] and he did. He seemed very spooked and said his passenger was as well. I saw him starting to turn towards the field and thought he could possibly descend rapidly back to the field. I told tower of the [situation] and as a precaution I told them to break him off the approach on a 270; thinking Aircraft Z was going to head straight at the airport that wasn't insight.The loss of separation comes from the 270 turn off final for Aircraft X and the departure of Aircraft Y on a 250 heading off of Runway 34. I initially thought I had enough lateral separation; then realized it was going to be closer than I assumed and when I saw it; not long after; turned both away from each other. I believe the lateral separation was 2.6 NM. After Aircraft Z [notified us]; I asked him what he wanted to do. I suggested a possible IFR pickup for radar vectors back to ROA for the ILS 34. He said an IFR pickup sounds like the best. I followed it by clearing him; since he was still climbing and was above the MVA in the area. It was when I tried to turn him final to join the approach he informed me that he wasn't IFR rated. We followed by giving him a vector to maintain until we found an airport with suitable VMC. I was unaware of specific phraseology in an IFR pickup; and thought suggesting IFR for an approach--with his agreement; meant he was qualified. I'm unaware that you can't suggest IFR like a SVFR to an aircraft.No recommendations; just reviewed 7110 Chapter 10 on VFR aircraft encountering bad weather.
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.