CEN09CA357 · Aviat A1 A
Aviat A1 A · Accident: hard landing
From Anoka County-Blaine (Janes Field) Airport (ANE) to Garrison, MN
Event
- NTSB case
- CEN09CA357
- 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
- Unknown
- 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 A1 A
- Aircraft type
- Aviat A1
- 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
- N190BA
- Operator
- Allan Dela
- Onboard fatalities
- Unknown
- Route
- From Anoka County-Blaine (Janes Field) Airport (ANE), Blaine, MNTo Garrison, MN
- Aircraft age
- Not recorded
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he attempted to land the float-equipped airplane on a lake with “glassy water” conditions. He made an approach to the lake where he could use the shoreline as a reference, and where some ripples on the surface of the lake made it possible for him to attempt a normal water landing. He reported that he “apparently” flew over the ripples. The nose of the right float hit the water first and the airplane started to porpoise. He pulled the nose up and added power to perform a go-around. He reported, “I believe the impact broke the right hand flying wires as the left wing dropped and that combined with the “P” factor turned the aircraft about 60 degrees to the left.” The airplane was approaching the shoreline so he cut the power. The airplane landed on the water and slid up the embankment with both wings impacting trees.
Probable cause
The pilot's improper flare, which resulted in a hard landing on the water and subsequent loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA357
- Event ID
- 20090615X65441
- Case number
- CEN09CA357
- 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. 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: 9fbc54d9256bf0d61b4a97242d489c7daec3d1374c34b930541859c2eaf454d9; retrieved 2026-09-15T11:26:43.264Z.