Hayward Executive Airport: Runway Incursions
194 reported incursions · 1 serious (Category A/B) · Hayward, CA
By year
- 20264
- 20253
- 202410
- 202311
- 202212
- 202115
- 20204
- 201913
- 201817
- 201720
- 201628
- 201528
- 20149
- 20131
- 20126
- 20112
- 20102
- 20095
- 20071
- 20061
- 20022
By severity category
- Category D — no immediate safety consequence122
- Category C — ample margin to avoid a collision47
- Other / pre-2008 classifications24
- Category A — serious, collision narrowly avoided1
By type
- Pilot deviation157
- Vehicle or pedestrian29
- Air traffic control7
- Other / unknown1
Serious incursions (Category A and B)
2018-12-03 · Hayward Executive Airport · EVOT / R22 · 10L · Category A
A/C 1 EVOT WAS OPERATING IFR AND HAD BEEN CLEARED FOR THE RNAV GPS APPROACH TO RUNWAY 28L. RUNWAYS 10 L/R WERE IN USE AT KHWD. NCT ATC OMITTED THE CLEARANCE TO CIRCLE TO RWY 10. LC INSTRUCTED A/C 1 TO CONTINUE INBOUND AND REPORT CIRCLING SOUTHBOUND FOR RUNWAY 10R. READ BACK CORRECT FROM A/C 1. A/C 1 STATES "I'LL TAKE 10L IF THAT'S OKAY?" LC ADVISES A/C 1 THAT HE HAS THEIR REQUEST. A/C 2 R22 WAS OPERATING IN THE PRACTICE VFR PATTERN ON RWY 10L. LC THEN ADVISED A/C 1 OF A/C 2 VIA A TRAFFIC CALL. A/C 1 REPORTED LOOKING FOR TRAFFIC. A/C 1 REPORTED THEIR CIRCLING MANEUVER. LC ADVISED A/C 2 OF A/C 1 VIA A TRAFFIC CALL. A/C 2 REPORTED LOOKING FOR A/C 1. A/C 1 WAS ONCE AGAIN ADVISED OF A/C 2 ON THE PARALLEL RUNWAY AND CLEARED TO LAND RUNWAY 10R. GOOD READ BACK FROM A/C 1. LC THEN COORDINATED WITH SCT TO ADVISE THEM THAT A/C 1 WOULD BE CIRCLING FOR RUNWAY 10R. A/C 2 WAS OPERATING OVER THE NUMBERS OF RUNWAY 10L AS A/C 1 ROLLED OUT ON FINAL AND LINED UP FOR THE WRONG RUNWAY, RUNWAY 10L. THE LC DETECTED THE EVENT AND ISSUED IMMEDIATE GO AROUND INSTRUCTIONS. A/C 1 REPORTED TAKING EVASIVE ACTION TO MISS A/C 2. THE CLOSEST PROXIMITY REPORTED WAS 50 TO 100 FEET LATERALLY AT THE SAME ALTITUDE. CONFLICT DETERMINED AS A/C 1 LINED UP FOR THE WRONG RUNWAY AND EXECUTED EVASIVE ACTION TO AVOID A/C 2 ON THE PARALLEL RUNWAY. NO SAFETY ALERTS WERE ISSUED.
Counts are reported events, not a danger ranking. Before FY2008 the FAA used a narrower definition, so earlier years are not directly comparable.
Source: FAA Runway Safety (RWS) database, via ASIAS · United States Government public domain.