37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1179561 |
Time | |
Date | 201406 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MRI.Airport |
State Reference | AK |
Aircraft 1 | |
Make Model Name | Light Sport Aircraft |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Aircraft 2 | |
Make Model Name | PA-23-250 Aztec |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) .7 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
A light sport aircraft inbound on campbell arrival [receiving] radar advisories with A11. Instructed to enter left base runway 25. A piper aztec departed runway 25 on campbell departure. Traffic was not issued with the aztec's takeoff clearance because the light sport was over campbell airstrip 110 knots on the campbell arrival and should not have been a conflict for the aztec per the lateral separation provided by the campbell departure. A radar replay showed that the light sport did not fly the campbell arrival correctly. From campbell airstrip he overflew tudor bus barn to providence hospital putting him in conflict with the aztec outbound via tudor bus barn on campbell departure. If he had flown the campbell arrival to the left base 25 over boniface as depicted; there would not have been a conflict. Aircraft reported inbound from the northwest; and A11 called on the land line regarding that aircraft. I relayed approach's information to the pilot and issued traffic for another aircraft inbound from the northwest. I did not return my scan back to the south until the light sport and the aztec passed; at which time the light sport reported near midair collision. The aztec was still on frequency and stated; 'it was not that close.'pilot forum explaining the imperativeness of flying arrival/departure procedures precisely. Maybe using radar replays or flight simulator depictions.
Original NASA ASRS Text
Title: MRI Controller reports of an aircraft that is supposed to follow a route into the airport and does not; while a departure reports having a NMAC with the arriving aircraft. Routes would have been separated if the arrival was following the prescribed route.
Narrative: A Light Sport aircraft inbound on Campbell Arrival [receiving] radar advisories with A11. Instructed to enter left base Runway 25. A Piper Aztec departed Runway 25 on Campbell Departure. Traffic was not issued with the Aztec's takeoff clearance because the Light Sport was over Campbell airstrip 110 knots on the Campbell arrival and should not have been a conflict for the Aztec per the lateral separation provided by the Campbell Departure. A radar replay showed that the Light Sport did not fly the Campbell Arrival correctly. From Campbell airstrip he overflew Tudor Bus Barn to Providence Hospital putting him in conflict with the Aztec outbound via Tudor Bus Barn on Campbell Departure. If he had flown the Campbell Arrival to the left base 25 over Boniface as depicted; there would not have been a conflict. Aircraft reported inbound from the northwest; and A11 called on the land line regarding that aircraft. I relayed Approach's information to the pilot and issued traffic for another aircraft inbound from the northwest. I did not return my scan back to the south until the Light Sport and the Aztec passed; at which time the Light Sport reported NMAC. The Aztec was still on frequency and stated; 'It was not that close.'Pilot forum explaining the imperativeness of flying arrival/departure procedures precisely. Maybe using radar replays or flight simulator depictions.
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.