Day developmental approach controller reported a near midair collision experienced by a SR22 being s...

Attributes
ACN	893938
Time
Date	201006
Local Time Of Day	0001-0600
Place
Locale Reference	I17.Airport
State Reference	OH
Aircraft 1
Make Model Name	SR22
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft
Flight Phase	Cruise
Route In Use	None
Person 1
Function	Approach Flight Data / Clearance Delivery
Qualification	Air Traffic Control Developmental
Person 2
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict NMAC Deviation - Procedural Published Material / Policy

Narrative:

An SR22 checked on 1-2 minutes after I took the position. I was sequencing three other SR22's into the airport and a regional jet; also giving en route services to three other aircraft IFR and VFR. After check on I gave the subject SR22 a 090 heading for sequencing. After about 5 miles and 1 minute he stated he had a near miss and had to turn to avoid what looked like an acrobatic aircraft. I immediately gave him traffic on the aerobatic aircraft which was at his 6 o'clock; 1 mile and 600 feet above him. He said that aircraft tail spun down through his altitude and created a near miss situation. The aerobatic aircraft was practicing inside a hot acrobatic box but was supposed to stay below 4500. This incident occurred at 5000. Recommendation; aerobatic aircraft must stay within the aerobatic box limitations.

Original NASA ASRS Text

Title: DAY developmental approach controller reported a NMAC experienced by a SR22 being sequenced to the airport; the reported conflict with an aerobatic aircraft performing maneuvers within an aerobatic box but above coordinated altitude/s.

Narrative: An SR22 checked on 1-2 minutes after I took the position. I was sequencing three other SR22's into the airport and a regional jet; also giving en route services to three other aircraft IFR and VFR. After check on I gave the subject SR22 a 090 heading for sequencing. After about 5 miles and 1 minute he stated he had a near miss and had to turn to avoid what looked like an acrobatic aircraft. I immediately gave him traffic on the aerobatic aircraft which was at his 6 o'clock; 1 mile and 600 feet above him. He said that aircraft tail spun down through his altitude and created a near miss situation. The aerobatic aircraft was practicing inside a hot acrobatic box but was supposed to stay below 4500. This incident occurred at 5000. Recommendation; aerobatic aircraft must stay within the aerobatic box limitations.

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.

Day developmental approach controller reported a near midair collision experienced by a SR22 being sequenced to the airport; the reported conflict with an aerobatic aircraft performing maneuvers within an aerobatic box but above coordinated altitude/s.