# Incident 20260802012229I: Textron Aviation Inc 172S, Hayward, CA, August 2, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 2, 2026, 18:20 local time
- Place: Hayward, CA
- Airport: Hayward Executive
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 37.6589° N, 122.1217° W: Placed by OpenAirDocs at HAYWARD EXEC (HWD), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.6589&lon=-122.1217&mi=10
- Aircraft: N363K, registered now (https://openairdocs.org/aircraft/N363K) (OpenAirDocs)
- Registry model: Textron 172S (registry code 2072449, https://openairdocs.org/model/textron-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: TEXTRON AVIATION INC 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 107 total, 32 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260802012229I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT STATEMENT:

"ON AUGUST 1, 2026, I WAS CONDUCTING AN UNSUPERVISED SOLO FLIGHT IN A CESSNA 172S EQUIPPED AT HAYWARD EXECUTIVE AIRPORT (KHWD). I WAS PRACTICING SHORT-FIELD LANDINGS IN THE TRAFFIC PATTERN FOR RUNWAY 28L.

PRIOR TO THE INCIDENT, I HAD COMPLETED 13 SUCCESSFUL LANDINGS IN THE PATTERN, MOST OF WHICH WERE STOP-AND-GO LANDINGS. I DID NOT EXPERIENCE ANY ISSUES WITH THE AIRCRAFT DURING THOSE PREVIOUS LANDINGS.

ON MY 14TH LANDING, THE AIRCRAFT TOUCHED DOWN NORMALLY. APPROXIMATELY 5–10 SECONDS AFTER TOUCHDOWN, DURING THE LANDING ROLLOUT, I EXPERIENCED WHAT APPEARED TO BE A LOCKING OF THE LEFT BRAKE. THE AIRCRAFT BEGAN TO GRADUALLY VEER TOWARD THE LEFT SIDE OF THE RUNWAY.

I MAINTAINED POSITIVE CONTROL OF THE AIRCRAFT AS IT MOVED TOWARD THE LEFT SIDE OF RUNWAY 28L. THE AIRCRAFT SUBSEQUENTLY LEFT THE PAVED RUNWAY SURFACE AND ENTERED THE GRASS AREA BETWEEN RUNWAY 28L AND TAXIWAY Z, BETWEEN TAXIWAYS A AND B.

DURING THE ROLLOUT MAY HAVE CONTRIBUTED TO THE LEFT BRAKE LOCKING AND THE SUBSEQUENT RUNWAY EXCURSION."

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.