# Incident 20240810013849I: Cessna 172N, Fremont, NE, August 10, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 10, 2024, 11:36 local time
- Place: Fremont, NE
- Airport: Fremont Municipal
- Damage: Minor damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: Pilot school (Part 141)
- Operator: 2OAS
- Location: 41.4499° N, 96.5212° W: Placed by OpenAirDocs at FREMONT MUNI (FET), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.4499&lon=-96.5212&mi=10
- Aircraft: N737SJ, registered now (https://openairdocs.org/aircraft/N737SJ) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 1,746 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240810013849I

## Narrative

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

ON THE MORNING OF 10 AUGUST 2024, THE PILOT WAS FLYING AIRCRAFT ^PRIVACY DATA OMITTED^ ON A TRAINING SORTIE DEMONSTRATING PATTERN OPERATIONS AT THE FREMONT AIRPORT, FREMONT, NEBRASKA (KFET).  THERE WERE 2 SOULS ON BOARD, THE PILOT AND STUDENT PILOT.  THE PILOT WAS FLYING THE AIRCRAFT.  WHILE PERFORMING A TAKEOFF ON RUNWAY 14 AT KFET AT APPROXIMATELY 300 FEET DOWN THE RUNWAY AT AN AIRSPEED OF 30-40 KTS (IAS) A FLOCK OF WHAT APPEARED TO BE CANDANIAN GEESE AROSE FROM THE LEFT SIDE OF THE RUNWAY IN SUCH A MANNER THE PILOT FELT THE BIRDS AND THE AIRCRAFT WERE ON A COLLISION COURSE AND ABORTED THE TAKEOFF.  THE PILOT PROCEEDED TO BREAK HARD IN AN ATTEMPT TO RAPIDLY DECELERATE IN ORDER TO NOT STRIKE THE BIRDS.  WHILE BREAKING, THE RIGHT MAIN TIRE RUPTURED CAUSING THE AIRCRAFT TO PULL TO THE RIGHT. THE AIRCRAFT DID NOT DEPART THE RUNWAY.  AFTER THE AIRCRAFT CAME TO A COMPLETE STOP,  THE PILOT SHUT DOWN THE AIRCRAFT AND CALLED THE MILLARD AIRPORT FBO-ORACLE AVIATION WITH INSTRUCTIONS TO CONTACT OMAHA TRACON TO INFORM THEM THAT THE AIRCRAFT WAS BLOCKING THE RUNWAY (RUNWAY 14 @ KFET).  OMAHA TRACON REACHED OUT TO THE PILOT VIA CELLPHONE AND HE WAS ABLE TO EXPLAIN THE EVENT IN DETAIL TO THE CONTROLLER.  FIELD MAINTENANCE CAME OUT TO THE AIRCRAFT, PUT A TEMPORARY WHEEL ON THE AIRCRAFT AND TOWED IT TO A FACILITY ON THE FIELD WHERE THE WHEEL ASSEMBLY WAS REPLACED.  AIRCRAFT WAS INSPECTED AND NO ADDITIONAL DAMAGE WAS FOUND.  A NASA REPORT WAS DRAFTED AND SUBMITTED ON 10 AUGUST 2024 DOCUMENTING THE EVENT.

## Other reports on N737SJ (1)

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

- [Incident 20220722013889I](https://openairdocs.org/incident/20220722013889I), Jul 22, 2022: Cessna 172N (N737SJ), Omaha, NE, Minor damage. On July 22, 2022 a student pilot operating [privacy data omitted], a Cessna 172, departed runway 12 at Millard Airport, Omaha, Nebraska. During landing…

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.