ERA25LA244 · Cessna 177B
Take Flight Holdings Cessna 177B · Accident: abnormal runway contact during landing
Event
- NTSB case
- ERA25LA244
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 177B
- Aircraft type
- Cessna 177
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N34655
- Operator
- Take Flight Holdings
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 52 years (built 1973)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot had planned to fly in the airport traffic pattern to practice takeoffs and landings. The pilot stated that during the first landing, after touchdown on the main wheels, he felt a “jolt” when the nosewheel came down and the airplane veered to the left and off the runway. To avoid a worker mowing in the vicinity, he initially applied the brakes and aft pressure on the control yoke in an attempt to slow the airplane. He then applied full right rudder and added power, and the airplane turned right, briefly became airborne as the airplane returned to the runway surface. The airplane then touched down “hard” on the nose landing gear and the pilot brought the airplane to a stop. The fuselage aft of the firewall was substantially damaged during the accident sequence. The worker who was mowing reported that he saw the airplane “wobbling” as it approached the runway. He then stopped cutting the grass and moved the mower closer to the airport perimeter fence to stay out of the airplane’s way. He continued to watch the airplane and described that during the landing it contacted the runway and bounced three times before he saw the airplane’s nose hit the ground, after which he watched it exit the runway.
Probable cause
A loss of control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA244
- Event ID
- 20250627200404
- Case number
- ERA25LA244
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d0a5043a94d67ec0604971767968c59b336bf1eebcfdbb0f33e07d328f88ebf7; retrieved 2026-09-16T20:00:45.786Z.