Mco local controller voiced concern regarding operational practice utilized by the TRACON that resul...

Attributes
ACN	850038
Time
Date	200909
Local Time Of Day	0601-1200
Place
Locale Reference	MCO.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Helicopter
Operating Under FAR Part	Part 91
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Non Radar 3 Air Traffic Control Time Certified In Pos 1 (mon) 1 Air Traffic Control Time Certified In Pos 1 (yrs) 1
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance
Miss Distance	Horizontal 6000 Vertical 400

Narrative:

F11 normally issues a crossing restriction of 2500 ft until south of orl VOR. Pilots operating on a visual approach typically follow the glideslope for the runway. This makes them cross the orl VOR at 2200 ft instead of 2500 ft. F11 had an operational error a few months ago involving this same type of operation; resulting in less than 300 ft horizontal by 0 ft vertical separation. I called the final controller working the airplane who was descending to alert him of the pending danger. A traffic alert was issued by the controller. We had several aircraft blow the crossing restriction; resulting in numerous conflict alerts; and two go-rounds for separation safety. We also had some pilot deviations called. In my opinion; the corridor between orl and mco needs to be sterile or redesign the airspace to make the class B airspace more restrictive of the general aviation pilots. This operation is unsafe and needs to be addressed.

Original NASA ASRS Text

Title: MCO Local Controller voiced concern regarding operational practice utilized by the TRACON that results in potential conflict events as described in this report; reporter suggested a more restrictive airspace redesign to preclude future events.

Narrative: F11 normally issues a crossing restriction of 2500 FT until south of ORL VOR. Pilots operating on a visual approach typically follow the glideslope for the runway. This makes them cross the ORL VOR at 2200 FT instead of 2500 FT. F11 had an operational error a few months ago involving this same type of operation; resulting in less than 300 FT horizontal by 0 FT vertical separation. I called the final controller working the airplane who was descending to alert him of the pending danger. A traffic alert was issued by the Controller. We had several aircraft blow the crossing restriction; resulting in numerous conflict alerts; and two go-rounds for separation safety. We also had some pilot deviations called. In my opinion; the corridor between ORL and MCO needs to be sterile or redesign the airspace to make the class B airspace more restrictive of the general aviation pilots. This operation is unsafe and needs to be addressed.

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.

Mco local controller voiced concern regarding operational practice utilized by the TRACON that results in potential conflict events as described in this report; reporter suggested a more restrictive airspace redesign to preclude future events.