 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower local controller described a helicopter/fixed wing conflict event as a helicopter crossed the runways; the reporter suggested increased and more specific internal coordination be mandated for these types of operations.
| Attributes | |
| ACN | 1136781 |
| Time | |
| Date | 201312 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Gulfstream IV / G350 / G450 |
| Flight Phase | Initial Climb |
| Route In Use | None |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Helicopter |
| Flight Phase | Cruise |
| Route In Use | None |
| Flight Plan | VFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I cleared the gulfstream iv for takeoff runway xxl and then observed him passing approximately 200 below a helicopter crossing both runways at midfield. This procedure was not coordinated with me. The position where local 1 is required to work during certain operations almost completely obscures the view of these subject crossings approaching from the west. Nearly all helicopter procedures for the west side of the airport fly to midfield at some point during the procedure. This makes it nearly impossible to decipher if a helicopter on the radar is a on the established procedure or not. Recommendation; these subject crossings be coordinated on the landline for runway xx operations only. Helicopter control is currently taught that giving a traffic call about landing traffic is optional. This call should be mandatory for both landing and departing traffic. Local control is taught not to call traffic about helicopters crossing in most situations. Local should give the traffic to landing and departing traffic.
Original NASA ASRS Text
Title: Tower Local Controller described a helicopter/fixed wing conflict event as a helicopter crossed the runways; the reporter suggested increased and more specific internal coordination be mandated for these types of operations.
Narrative: I cleared the Gulfstream IV for takeoff Runway XXL and then observed him passing approximately 200 below a helicopter crossing both runways at midfield. This procedure was not coordinated with me. The position where Local 1 is required to work during certain operations almost completely obscures the view of these subject crossings approaching from the west. Nearly all helicopter procedures for the west side of the airport fly to midfield at some point during the procedure. This makes it nearly impossible to decipher if a helicopter on the RADAR is a on the established procedure or not. Recommendation; these subject crossings be coordinated on the landline for Runway XX operations only. Helicopter control is currently taught that giving a traffic call about landing traffic is optional. This call should be mandatory for both landing and departing traffic. Local Control is taught not to call traffic about helicopters crossing in most situations. Local should give the traffic to landing and departing traffic.
Data retrieved from NASA's ASRS site as of July 2013 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.