 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
F11 controler reports of class bravo violations which are being worked by mco tower and not pointed out to the F11 controller.
| Attributes | |
| ACN | 1208486 |
| Time | |
| Date | 201410 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | MCO.Airport |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Helicopter |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | VFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
| Events | |
| Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X on ILS 18R; switched to mco tower 11 north of mco; at the same time working 5 other aircraft turning on the approach. When I got done clearing an air carrier for the approach; I noticed aircraft X was in conflict with aircraft Y; 3 north of mco at 800 feet on a 3W (mco tower tag); talking to the local west controller 3W tag; targets merged with no point out. I was startled and I called a flm over to question the operation. Last time this happened I was tagged with a category a error. The flm acted as if he did not want to pursue or take action against the tower controller. Then when the tower controller pointed out aircraft Y 5 minutes later after 5 or 6 more arrivals go by; I said traffic observed; and that's when I was spoken to about wrong phraseology to the tower controller. This facility is allowing more and more helicopters; picture takers; aerial surveyors and law enforcement into bravo airspace and creating more unsafe operations compromising safety for special accommodations. The opinion of controllers is disregarded in consideration of these operations.
Original NASA ASRS Text
Title: F11 Controler reports of Class Bravo violations which are being worked by MCO Tower and not pointed out to the F11 Controller.
Narrative: Aircraft X on ILS 18R; switched to MCO tower 11 N of MCO; at the same time working 5 other aircraft turning on the approach. When I got done clearing an air carrier for the approach; I noticed Aircraft X was in conflict with Aircraft Y; 3 north of MCO at 800 feet on a 3W (MCO Tower tag); talking to the local west controller 3W tag; targets merged with no point out. I was startled and I called a FLM over to question the operation. Last time this happened I was tagged with a category A error. The FLM acted as if he did not want to pursue or take action against the tower controller. Then when the tower controller pointed out Aircraft Y 5 minutes later after 5 or 6 more arrivals go by; I said traffic observed; and that's when I was spoken to about wrong phraseology to the tower controller. This facility is allowing more and more helicopters; picture takers; aerial surveyors and law enforcement into Bravo airspace and creating more unsafe operations compromising safety for special accommodations. The opinion of controllers is disregarded in consideration of these operations.
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.