OpenAirDocs.org

20260802012229I

Incident · Minor damage
Open the Markdown

FAA incident report · Textron 172S · Hayward, CA · August 2, 2026

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
August 2, 2026 · 18:20 local
Place
Hayward, CA
Airport
Hayward Executive
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N363K
Reported as
Textron 172S
Reported engine
Lycoming IO-360-L2A
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Student
Pilot’s flight hours
107 total32 in the last 90 days
N363KRegistered now · Textron 172SS/N 172S12195 · Built 2018Airframe modelTextron 172SEngine modelLycoming IO-360-L2AReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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."

As the FAA filed it

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."