 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ito local controller is frustrated with local coordination procedure and non issuance of conflicting traffic.
| Attributes | |
| ACN | 618438 |
| Time | |
| Date | 200405 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : ito.airport |
| State Reference | HI |
| Altitude | msl single value : 1500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : ito.tracon tower : ito.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B717 (Formerly MD-95) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach descent : intermediate altitude |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : ito.tracon tower : ito.tower |
| Operator | common carrier : air taxi |
| Make Model Name | AS 350 Astar/Ecureuil |
| Operating Under FAR Part | Part 135 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : radar |
| Experience | controller radar : 12 controller time certified in position1 : 2 controller time certified in position2 : 8 |
| ASRS Report | 618438 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure |
| Independent Detector | atc equipment : conflict alert aircraft equipment : tcas other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Miss Distance | horizontal : 3000 vertical : 1 |
| Supplementary | |
| Problem Areas | ATC Human Performance Airspace Structure FAA |
| Primary Problem | Airspace Structure |
| Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
The air carrier X jet called me on tower without having been issued the outbound traffic (opposite direction). The helicopter also had not been issued a traffic call. When the jet called, I issued the traffic, but it should have been a traffic alert. This situation is happening routinely at my facility (due to communication change points and inattention). The airspace is shared in control responsibility and the jet arrival corridor has many helicopter's and fixed wings arriving/departing/transitioning. We have a tracab and very loose procedures.
Original NASA ASRS Text
Title: ITO LCL CTLR IS FRUSTRATED WITH LCL COORD PROC AND NON ISSUANCE OF CONFLICTING TFC.
Narrative: THE ACR X JET CALLED ME ON TWR WITHOUT HAVING BEEN ISSUED THE OUTBOUND TFC (OPPOSITE DIRECTION). THE HELI ALSO HAD NOT BEEN ISSUED A TFC CALL. WHEN THE JET CALLED, I ISSUED THE TFC, BUT IT SHOULD HAVE BEEN A TFC ALERT. THIS SIT IS HAPPENING ROUTINELY AT MY FACILITY (DUE TO COM CHANGE POINTS AND INATTENTION). THE AIRSPACE IS SHARED IN CTL RESPONSIBILITY AND THE JET ARR CORRIDOR HAS MANY HELI'S AND FIXED WINGS ARRIVING/DEPARTING/TRANSITIONING. WE HAVE A TRACAB AND VERY LOOSE PROCS.
Data retrieved from NASA's ASRS site as of July 2007 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.