FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA26LA075 · Aviat Aircraft Inc A-1C-200

20 Dec 2025 · Hawthorne, FL, United States

Aviat Aircraft Inc A-1C-200 · Accident: hard landing

From Leeward Air Ranch Airport (FD04) to an unrecorded destination

Report a problem

Event

NTSB case
ERA26LA075
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

Aviat Aircraft Inc A-1C-200

Aircraft type
Aviat A-1
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
N656B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Leeward Air Ranch Airport (FD04), Ocala, FLTo not recorded
Aircraft age
About 12 years (built 2013)
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
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
Hard landing
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
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The purpose of the flight was for the pilot to depart from a paved airport in the amphibious airplane and fly to a nearby lake and land. The pilot overflew the lake and noticed the water appeared to be “glassy” in sections. During touchdown, the airplane landed hard, which resulted in substantial damage to its wings and fuselage. The airplane came to rest, partially submerged, in the lake. The pilot stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain an appropriate descent rate for a glassy water landing, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA26LA075
Event ID
20251223202199
Case number
ERA26LA075
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, 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: c8d3b639912743f9ad85e7c40e1cfc87c887445f740886f2369a701cc7a1c93f; retrieved 2026-09-16T20:37:34.998Z.