# Accident 20260623009912A: Cessna 172S, Brooksville, FL, June 23, 2026

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 23, 2026, 08:57 local time
- Place: Brooksville, FL
- Airport: Brooksville-Tampa Bay Regional
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Run-Up Area
- 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: N413AA, registered now (https://openairdocs.org/aircraft/N413AA) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360 series (registry code 41881, https://openairdocs.org/engine/lycoming-io-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- 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/20260623009912A

## Narrative

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

AIRCRAFT #1 WAS STRUCK FROM BEHIND BY AIRCRAFT #2 WHILE PERFORMING PRETAXI CHECKLIST.

## Other aircraft in the event

- N9417Z, Cessna 172R: [Incident 20260623008462I](https://openairdocs.org/incident/20260623008462I)

## 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 (N413AA), Brooksville, FL, substantial 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.

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.