37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1184783 |
Time | |
Date | 201407 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SNA.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Helicopter |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 14 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was working local 1. I had a helicopter call me inbound 5 southeast of the field. Told him to report 1 mile west of the field and asked him his landing request. He told me at a local FBO for fuel. I asked him which one and the helicopter continued inbound. I had an air carrier on about a 7 mile final at this point. When the helicopter got closer to the airport I coordinated with the other local control for a taxiway alpha abeam the FBO landing and also with ground control. I told the helicopter to cross directly over the tower and make a right turn over taxiway alpha cleared to land taxiway alpha abeam the FBO. I informed the air carrier of the helicopter and told him the [traffic] was 1 o'clock and 3 miles. I then informed the helicopter of traffic departing runway 19L (a small aircraft). As the helicopter crossed over the tower he started to descend directly for taxiway alpha and would have gotten close to the small aircraft. I informed the helicopter to stop his descent for the small aircraft and the other local cancelled the takeoff of the cessna. (The issue is I did not give an altitude restriction to the helicopter; which put him in close proximity of the small aircraft).recommend to have established helicopter procedures published for all helicopters inbound to sna to stop the issue from happening. This is not the first time at sna that we have had issues with helicopters.
Original NASA ASRS Text
Title: SNA Tower Controller reports of route problem into SNA involving helicopters conflicting with normal flow if traffic.
Narrative: I was working Local 1. I had a helicopter call me inbound 5 southeast of the field. Told him to report 1 mile west of the field and asked him his landing request. He told me at a local FBO for fuel. I asked him which one and the helicopter continued inbound. I had an Air Carrier on about a 7 mile final at this point. When the helicopter got closer to the airport I coordinated with the other Local Control for a Taxiway Alpha abeam the FBO landing and also with Ground Control. I told the helicopter to cross directly over the Tower and make a right turn over Taxiway Alpha cleared to land Taxiway Alpha abeam the FBO. I informed the Air Carrier of the helicopter and told him the [traffic] was 1 o'clock and 3 miles. I then informed the helicopter of traffic departing Runway 19L (a small aircraft). As the helicopter crossed over the Tower he started to descend directly for Taxiway Alpha and would have gotten close to the small aircraft. I informed the helicopter to stop his descent for the small aircraft and the other Local cancelled the takeoff of the Cessna. (The issue is I did not give an altitude restriction to the helicopter; which put him in close proximity of the small aircraft).Recommend to have established helicopter procedures published for all helicopters inbound to SNA to stop the issue from happening. This is not the first time at SNA that we have had issues with helicopters.
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.