# Incident 20260623008462I: Cessna 172R, Brooksville, FL, June 23, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 23, 2026, 08:57 local time
- Place: Brooksville, FL
- Airport: Brooksville-Tampa Bay Regional
- Damage: Minor damage
- Collision: Collision on the ground
- Phase of flight: Taxi
- Operating rules: Pilot school (Part 141)
- Location: 28.4740° N, 82.4465° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=28.4740&lon=-82.4465&mi=10
- Aircraft: N9417Z, registered now (https://openairdocs.org/aircraft/N9417Z) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0-360-B1E (registry code 41559, https://openairdocs.org/engine/lycoming-i0-360-b1e) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING I0-360-B1E
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 23 total, 4 in this make and model, 18 in the last 90 days
- NTSB investigation: [NTSB ERA26LA248](https://openairdocs.org/ntsb/ERA26LA248) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260623008462I

## Narrative

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

AIRCRAFT #1 STRUCK AIRCRAFT # 2 FROM BEHIND WHILE TAXING

## Other aircraft in the event

- N413AA, Cessna 172S: [Accident 20260623009912A](https://openairdocs.org/incident/20260623009912A)

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA26LA248](https://openairdocs.org/ntsb/ERA26LA248), Jun 23, 2026: Cessna 172 (N9417Z), Brooksville, FL, minor damage. Probable cause: The student pilot’s failure to ensure clearance while taxiing, which resulted in contact with another airplane that was performing an engine run-up.

## Other reports on N9417Z (3)

Matched to the same aircraft by N-number and date.

- [Incident 20260516010179I](https://openairdocs.org/incident/20260516010179I), May 16, 2026: Cessna 172R (N9417Z), Brooksville, FL, No damage. Student pilot stated that after the airplane landed, the aircraft suddenly drifted to the right of the runway and came to a stop in the grass. Verbally over…
- [Incident 20171211022979I](https://openairdocs.org/incident/20171211022979I), Dec 11, 2017: Cessna 172R (N9417Z), Brooksville, FL, Minor damage. On December 11, 2017, at 1100 EST a Cessna aircraft, CO., model 172R, N9417Z that is registered to American aviation inc., had a propeller strike against a…
- [Accident 20140305001819A](https://openairdocs.org/incident/20140305001819A), Mar 5, 2014: Cessna 172R (N9417Z), Jackson, TN, Substantial damage. On March 5, 2014, aircraft N9417Z, a Cessna 172, departed on an IFR flight from mkl to ags. At 10:33 am, the mkl tower received an emergency call from the…

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.