 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ads controller described potential conflict event involving an IFR over flight and a VFR departure aircraft; reporter indicted they should have issued traffic to the departure prior to frequency change.
| Attributes | |
| ACN | 874004 |
| Time | |
| Date | 201002 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ADS.Airport |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | Skylane 182/RG Turbo Skylane/RG |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise Initial Climb |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Baron 55/Cochise |
| Flight Phase | Cruise |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
It was very slow and approach called me on the shout line and requested a descent for aircraft Y going into dal. Normally they are capped at 3;000; but since I didn't have any departures I gave control. Aircraft Y was about 7 miles away when this happened. Aircraft X calls me later ready for VFR flight following and I cleared him and assigned maintain VFR at or below 2;000. They take off and I switched them to departure. I then noticed aircraft Y at 020 and aircraft X was at 015; the were both now talking to departure. Out the window it looked find and aircraft Y passed behind the VFR aircraft X and there was 400-500 ft between them vertically. If they had both been IFR this would have been an error. The story on the scope looked worse than outside since the ca (conflict alert) was going off. It is the pilots responsibility to see and avoid when IFR but I wish I had told him about the traffic before hand even though I thought the crossing traffic would; and did; pass behind him. Recommendation; I will force myself to stay 100% focused even when it is slow.
Original NASA ASRS Text
Title: ADS Controller described potential conflict event involving an IFR over flight and a VFR departure aircraft; reporter indicted they should have issued traffic to the departure prior to frequency change.
Narrative: It was very slow and approach called me on the shout line and requested a descent for Aircraft Y going into DAL. Normally they are capped at 3;000; but since I didn't have any departures I gave control. Aircraft Y was about 7 miles away when this happened. Aircraft X calls me later ready for VFR flight following and I cleared him and assigned maintain VFR at or below 2;000. They take off and I switched them to Departure. I then noticed Aircraft Y at 020 and Aircraft X was at 015; the were both now talking to Departure. Out the window it looked find and Aircraft Y passed behind the VFR Aircraft X and there was 400-500 FT between them vertically. If they had both been IFR this would have been an error. The story on the scope looked worse than outside since the CA (conflict alert) was going off. It is the pilots responsibility to See and Avoid when IFR but I wish I had told him about the traffic before hand even though I thought the crossing traffic would; and did; pass behind him. Recommendation; I will force myself to stay 100% focused even when it is slow.
Data retrieved from NASA's ASRS site as of April 2012 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.