![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1123657 |
| Time | |
| Date | 201310 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | CVG.TRACON |
| State Reference | KY |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Person 1 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
During an arrival push; while working arrivals; a crj-200 was inbound to cvg via the tigrr fix at 110; heading approximately 230. When the crj was 1 mile from my boundary; I noticed an untagged aircraft; on a discrete beacon code; 7 miles southwest of the crj's position; indicating 100; eastbound. I gave the crj a vector of heading 255 and immediately issued traffic. As soon as I issued the vector; I noticed the target appeared to have turned northbound and was still climbing. I issued a vector of H270 to the crj and once again issued the traffic; this time at 12 o'clock and 2 miles; out of 106 and still climbing. My trainer stepped in and issued a traffic alert and a climb to the crj; who then told us he was responding to a RA and would miss the aircraft by 1;000 feet. Recommendation; I suspect this unknown aircraft was a skydiving aircraft; operating out of waynesville airport; which our facility does not have a LOA with. This company needs to be notified that even if they are VFR; anything above 100 is a bad place to be at the inbound fix. I'm not sure why the aircraft was on a discrete code; or who was working the aircraft.
Original NASA ASRS Text
Title: CVG Controller described a TCAS RA event between an IFR air carrier arrival and a non-identified target on a discrete code a likely skydiving aircraft.
Narrative: During an arrival push; while working arrivals; a CRJ-200 was inbound to CVG via the TIGRR fix at 110; heading approximately 230. When the CRJ was 1 mile from my boundary; I noticed an untagged aircraft; on a discrete beacon code; 7 miles SW of the CRJ's position; indicating 100; eastbound. I gave the CRJ a vector of heading 255 and immediately issued traffic. As soon as I issued the vector; I noticed the target appeared to have turned northbound and was still climbing. I issued a vector of H270 to the CRJ and once again issued the traffic; this time at 12 o'clock and 2 miles; out of 106 and still climbing. My trainer stepped in and issued a traffic alert and a climb to the CRJ; who then told us he was responding to a RA and would miss the aircraft by 1;000 feet. Recommendation; I suspect this unknown aircraft was a skydiving aircraft; operating out of Waynesville airport; which our facility does not have a LOA with. This company needs to be notified that even if they are VFR; anything above 100 is a bad place to be at the inbound fix. I'm not sure why the aircraft was on a discrete code; or who was working the aircraft.
Data retrieved from NASA's ASRS site as of July 2013 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.