37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 717576 |
Time | |
Date | 200611 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : orl.vortac |
State Reference | FL |
Altitude | msl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mco.tracon tower : den.tower |
Operator | general aviation : personal |
Make Model Name | Bonanza 36 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Aircraft 2 | |
Controlling Facilities | tracon : mco.tracon |
Operator | general aviation : personal |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Experience | controller radar : 20 controller time certified in position1 : 12 |
ASRS Report | 717576 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot |
Events | |
Anomaly | conflict : airborne critical |
Independent Detector | atc equipment : conflict alert other controllera |
Resolutory Action | controller : issued new clearance controller : issued alert flight crew : took evasive action |
Supplementary | |
Problem Areas | FAA |
Primary Problem | FAA |
Situations | |
ATC Facility | procedure or policy : mco.tracon |
Narrative:
There is a procedure in place in the LOA between orl tower and mco approach that allows orl tower to issue discrete beacon codes to VFR aircraft requesting VFR service. These aircraft are turned on course after departure and switched to departure control. The departure controller does not know these aircraft are coming. The pilot mistakenly thinks he is getting radar service off the ground. In this incident; I had taken a pointout on the BE35 VFR landing orl. The pase called 'with you' and I had no information on this aircraft. As the pase acquired; he was in immediate conflict with BE35; which was on orl tower frequency. I issued a traffic alert and recommended an immediate turn. The pilot saw the BE35 and resumed his own navigation. The pilot was not happy with this situation. The tower did not exchange traffic. Corrective action: if controllers are forced to continue to use this procedure; these aircraft should be put on headings that will not conflict with other aircraft. Otherwise; this procedure should be suspended requiring the pilots to call approach directly to request radar service.
Original NASA ASRS Text
Title: MCO CTLR DESCRIBED CONFLICT BTWN 2 ACFT AT 1500 FT ALLEGING PROC BTWN TWR AND TRACON AS CAUSAL FACTOR.
Narrative: THERE IS A PROC IN PLACE IN THE LOA BTWN ORL TWR AND MCO APCH THAT ALLOWS ORL TWR TO ISSUE DISCRETE BEACON CODES TO VFR ACFT REQUESTING VFR SVC. THESE ACFT ARE TURNED ON COURSE AFTER DEP AND SWITCHED TO DEP CTL. THE DEP CTLR DOES NOT KNOW THESE ACFT ARE COMING. THE PLT MISTAKENLY THINKS HE IS GETTING RADAR SVC OFF THE GND. IN THIS INCIDENT; I HAD TAKEN A POINTOUT ON THE BE35 VFR LNDG ORL. THE PASE CALLED 'WITH YOU' AND I HAD NO INFO ON THIS ACFT. AS THE PASE ACQUIRED; HE WAS IN IMMEDIATE CONFLICT WITH BE35; WHICH WAS ON ORL TWR FREQ. I ISSUED A TFC ALERT AND RECOMMENDED AN IMMEDIATE TURN. THE PLT SAW THE BE35 AND RESUMED HIS OWN NAV. THE PLT WAS NOT HAPPY WITH THIS SITUATION. THE TWR DID NOT EXCHANGE TFC. CORRECTIVE ACTION: IF CTLRS ARE FORCED TO CONTINUE TO USE THIS PROC; THESE ACFT SHOULD BE PUT ON HDGS THAT WILL NOT CONFLICT WITH OTHER ACFT. OTHERWISE; THIS PROC SHOULD BE SUSPENDED REQUIRING THE PLTS TO CALL APCH DIRECTLY TO REQUEST RADAR SVC.
Data retrieved from NASA's ASRS site as of January 2009 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.