37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1205777 |
Time | |
Date | 201409 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ROA.TRACON |
State Reference | VA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Instructor Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 18 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
The lynchburg west radar position has become increasingly difficult with a very high amount of flight training occurring daily. Aircraft X was on a round robin flight plan from lyh to lyh for the purposes on practice approaches. Aircraft Y was an IFR departure routed lyh to dan which is about a 200 degree heading. We had just taken the position relief briefing and there was a high volume of traffic. Aircraft X was on the published missed approach for the ILS runway 4 and was climbing to 3;000 ft on about a 060 degree heading. The lyh tower called for release of aircraft Y and called him rolling on a 010 heading. Aircraft X wanted to proceed to the lyh VOR for a full procedure VOR runway 4 approach. The developmental climbed aircraft X to 4;000 ft and turned them right to a 190 degree heading. Aircraft Y checked in and the developmental climbed them to 4;000 ft on a 140 degree heading. They had about 3.5 miles separation with diverging headings and matched speeds; so I felt this was a safe operation. There were several other things going on at the time and my attention was diverted for a short time. The developmental turned aircraft X right to the lyh VOR; about a 250 degree heading still at 4;000 ft; this decreased separation but we still had diverging headings. The developmental then cleared aircraft Y direct to dan; which was about 200 degrees and we no longer had legal separation. I told the developmental to descend aircraft X to 3;000 ft and turn aircraft Y back to the left. Aircraft X started to descend but aircraft Y didn't understand the instructions but stated that they had the other aircraft in sight. Aircraft Y was instructed to maintain visual separation with aircraft X and proceed direct dan. The minimum amount of separation was about 1.5 miles. The developmental explained to me that he/she got dan confused with the sbv VOR which was about a 150 heading and would have fine for separation.a flight started school a couple of years ago and traffic is increasing exponentially. They currently have [a number of] practice areas which will soon expand and [they] are adding new aircraft and instructors every month. The volume of traffic has increased to a point where it's becoming managed chaos and close calls are becoming more numerous. We have been discussing ways to lighten the workload at this sector including possibly splitting the sector; limiting traffic advisories in the practice areas etc. This all takes time; I understand; but meaningful training is almost impossible because so much time is spent making traffic calls. We took over this airspace 10 years ago and it was never designed for this amount of traffic and there are no procedures in place to split the sector this should be a high priority before a mid air happens.
Original NASA ASRS Text
Title: ROA TRACON Controller reports of an airborne conflict caused by the Developmental becoming confused and issuing an incorrect heading.
Narrative: The Lynchburg West Radar position has become increasingly difficult with a very high amount of flight training occurring daily. Aircraft X was on a round robin flight plan from LYH to LYH for the purposes on practice approaches. Aircraft Y was an IFR departure routed LYH to DAN which is about a 200 degree heading. We had just taken the position relief briefing and there was a high volume of traffic. Aircraft X was on the published missed approach for the ILS Runway 4 and was climbing to 3;000 FT on about a 060 degree heading. The LYH Tower called for release of Aircraft Y and called him rolling on a 010 heading. Aircraft X wanted to proceed to the LYH VOR for a full procedure VOR Runway 4 approach. The developmental climbed Aircraft X to 4;000 FT and turned them right to a 190 degree heading. Aircraft Y checked in and the developmental climbed them to 4;000 FT on a 140 degree heading. They had about 3.5 miles separation with diverging headings and matched speeds; so I felt this was a safe operation. There were several other things going on at the time and my attention was diverted for a short time. The developmental turned Aircraft X right to the LYH VOR; about a 250 degree heading still at 4;000 FT; this decreased separation but we still had diverging headings. The developmental then cleared Aircraft Y direct to DAN; which was about 200 degrees and we no longer had legal separation. I told the developmental to descend Aircraft X to 3;000 FT and turn Aircraft Y back to the left. Aircraft X started to descend but Aircraft Y didn't understand the instructions but stated that they had the other aircraft in sight. Aircraft Y was instructed to maintain visual separation with Aircraft X and proceed direct DAN. The minimum amount of separation was about 1.5 miles. The developmental explained to me that he/she got DAN confused with the SBV VOR which was about a 150 heading and would have fine for separation.A flight started school a couple of years ago and traffic is increasing exponentially. They currently have [a number of] practice areas which will soon expand and [they] are adding new aircraft and instructors every month. The volume of traffic has increased to a point where it's becoming managed chaos and close calls are becoming more numerous. We have been discussing ways to lighten the workload at this sector including possibly splitting the sector; limiting traffic advisories in the practice areas etc. This all takes time; I understand; but meaningful training is almost impossible because so much time is spent making traffic calls. We took over this airspace 10 years ago and it was never designed for this amount of traffic and there are no procedures in place to split the sector this should be a high priority before a mid air happens.
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.