Hio controller reports of an airborne conflict between two helicopters and the lack of coordination ...

Attributes
ACN	1231088
Time
Date	201501
Local Time Of Day	1201-1800
Place
Locale Reference	HIO.Tower
State Reference	OR
Environment
Light	Dusk
Aircraft 1
Make Model Name	Helicopter
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	None
Aircraft 2
Make Model Name	Helicopter
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	None
Flight Plan	VFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3
Person 2
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (mon) 6
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict NMAC Deviation - Procedural Published Material / Policy

Narrative:

While working controller in charge; I was working with the hillsboro fire department personnel in the tower cab checking on the communication radio when I heard the local 2 controller say something about traffic over alpha in his airspace. As I looked up there was another helicopter talking to the other local controller that had been departed westbound via the alpha taxiway. I told the local controller that the alpha pattern was hot. Later the pilot of aircraft X called and said that she got within 100 ft. Of the other 1st; the preferred departure routing for noise with the port of portland is westbound over the alpha taxiway. This regularly conflicts with other helicopter traffic in the alpha helicopter patters working on a different frequency with another controller. A different departure route should be used.2nd; currently there is no requirement to verbally coordinate via landline coordination to cross through another controllers airspace within the facility. All use of another controller's airspace should be coordinated via the landline between local control positions.

Original NASA ASRS Text

Title: HIO Controller reports of an airborne conflict between two helicopters and the lack of coordination required by Tower SOP to enter or use another position's airspace.

Narrative: While working CIC; I was working with the Hillsboro fire department personnel in the tower cab checking on the communication radio when I heard the local 2 controller say something about traffic over alpha in his airspace. As I looked up there was another helicopter talking to the other local controller that had been departed westbound via the alpha taxiway. I told the local controller that the alpha pattern was hot. Later the pilot of Aircraft X called and said that she got within 100 ft. of the other 1st; the preferred departure routing for noise with the port of Portland is westbound over the alpha taxiway. This regularly conflicts with other helicopter traffic in the alpha helicopter patters working on a different frequency with another controller. A different departure route should be used.2nd; currently there is no requirement to verbally coordinate via landline coordination to cross through another controllers airspace within the facility. All use of another controller's airspace should be coordinated via the landline between local control positions.

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.

Hio controller reports of an airborne conflict between two helicopters and the lack of coordination required by tower SOP to enter or use another position's airspace.