CEN20LA207 · Icon A5
Icon A5 · Accident: part(s) separation from aircraft during takeoff
From Sky Harbor Airport (KDYT) to Sky Harbor Airport (KDYT)
Event
- NTSB case
- CEN20LA207
- 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
Icon A5
- Aircraft type
- Icon A5
- 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
- N838BA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sky Harbor Airport (KDYT), Duluth, MNTo Sky Harbor Airport (KDYT), Duluth, MN
- Aircraft age
- About 1 year (built 2019)
- 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
- Takeoff
- 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
- Part(s) separation from aircraft
- 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 propeller/rotor
- Environmental issues › Physical environment
- Personnel issues › Action/decision
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 taxied the amphibian airplane downwind on the water for takeoff. When facing into the wind, he applied full power; about 5 seconds later, he heard a "loud bang." The propeller blades separated and penetrated the fuselage, resulting in substantial damage to the airplane's fuselage. The pilot reported that, immediately before the accident flight, he had placed a portable speaker on the top of the airplane and did not recall removing the speaker before departure. The pilot stated, "the speaker must have rolled over the engine compartment and into the propellers." It is likely that the audio speaker, which was left on the airplane, struck the propeller blades, which resulted in the propeller blades separating from the propeller and penetrating the fuselage.
Probable cause
The pilot’s failure to remove an object from the airplane’s exterior, which impacted the propeller blades when he applied full power, causing them to fracture and damage the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA207
- Event ID
- 20200604X90229
- Case number
- CEN20LA207
- 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. 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: 6b5a58d3b33693e69c8ca3c108c166a4699c0f34c05ad50bfcc6128710ff8933; retrieved 2026-09-16T11:46:16.837Z.