COORD BREAKDOWN BETWEEN HWD TWR AND OAK NORTH AND SOUTH TWRS.

1988-06 · NASA ASRS report 88751

Date: 1988-06 · Aircraft: Helicopter · Phase: cruise

Anomalies: other-airspace-violation-entry-or-exit|other-unspecified

Synopsis

COORD BREAKDOWN BETWEEN HWD TWR AND OAK NORTH AND SOUTH TWRS.

Narrative

FROM A POS WELL S OF HWD ATA; I REQUESTED AND RECEIVED PERMISSION TO TRANSITION THROUGH HAYWARD TO A LNDG AT OAK. HWD ASKED WHERE AT OAK I WAS LNDG; ISSUED ME A TRANSPONDER CODE; AND ADVISED ME THAT I WAS CLRED AS REQUESTED (BAY SHORELINE; 500'; TO OAK N FIELD SPOT ECHO). UPON REACHING THE APPROX W END OF THE HWD TFC PATTERN AREA WITH OAK IN SIGHT; I REQUESTED AND RECEIVED A FREQ CHANGE TO OAK. UPON CALL UP; OAK ISSUED US A NEW TRANSPONDER CODE; AND WHEN WE IDENTED; ADMONISHED US FOR BEING WELL WITHIN THE OAK ARSA; LINED UP WITH THE FINAL APCH COURSE (I WASN'T); AND THAT I SHOULD CALL OAK N TWR. I MENTIONED THAT I HAD BEEN TALKING TO HWD; BUT SAID NO MORE; INSTEAD MAKING THE INSTRUCTED FREQ CHANGE AND CONTINUING TO A LNDG AT OAK. CLEARLY; THE REACTION OF THE FIRST OAK TWR CTLR CONVINCED ME THAT HWD TWR HAD FUMBLED THE HDOF. OAK APPARENTLY DIDN'T KNOW I WAS COMING; AND WAS UNDERSTANDABLY AGITATED; ALTHOUGH THERE WAS NO CONFLICT WITH OTHER ACFT. IF THERE IS A GENERAL PROB WITH HDOFS BTWN OVERLAPPING ATA'S; OR ATA/ARSA OVERLAPS; THE TWR CTLR ISSUING A TRANSITION CLRNC MUST COMMUNICATE WITH THE ADJOINING FAC OR ELSE TELL THE INVOLVED ACFT TO 'REMAIN CLR.' OTHERWISE; 'CLRED AS REQUESTED' WILL SET UP A TRUSTING PLT FOR AN AIRSPACE VIOLATION. PERHAPS THE JURISDICTIONAL SIDE DEALS THAT EXIST BTWN ADJACENT FACS (IE; HWD; OAK AND BAY APCH ALL OWN CERTAIN AIRSPACE OVER THE SEAM BTWN THEM) SHOULD BE PUBLISHED SO THAT INTERESTED PLTS CAN BE IN ON THE SIDE DEALS THAT DON'T APPEAR ON SECTIONAL OR TCA CHARTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR DID NOT FOLLOW UP BY CALLING THE TWR SUPVR ON THE TELEPHONE. RPTR BELIEVES THE MOST FEASIBLE EXPLANATION AS TO WHY THE S TWR RADAR POS WAS SURPRISED BY THIS HELI'S CALL AND UNAWARE OF HIS POS IS THAT THE COORD DONE BY HWD TWR WAS DONE WITH THE N TWR AT OAK. THIS IS WHERE THE HELI WAS DESTINED AND ALTHOUGH THE HELI WAS ENTERING S TWR'S AIRSPACE AND SHOULD HAVE BEEN COORDINATED WITH THEM; THE N TWR SEEMED TO BE THE ONE THAT KNEW ABOUT THE HELI'S APCH. RPTR HAS RECEIVED NO FURTHER COM WITH FAA ABOUT THIS INCIDENT AND ASSUMES THAT THE MATTER HAS BEEN DROPPED. RPTR'S STATEMENT THAT HE HAD BEEN WORKING WITH HWD TWR WAS APPARENTLY ENOUGH TO SATISFY OAK TWR.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.