CEN20CA177 · M-Squared Sport 1000
M-Squared Sport 1000 · Accident: loss of control in flight during takeoff
From Little Falls-Morrison County-Lindbergh field (LXL) to Little Falls-Morrison County-Lindbergh field (LXL)
Event
- NTSB case
- CEN20CA177
- 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
M-Squared Sport 1000
- Aircraft type
- M Squared SPORT 1000
- 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
- N7013W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Little Falls-Morrison County-Lindbergh field (LXL), Little Falls, MNTo Little Falls-Morrison County-Lindbergh field (LXL), Little Falls, MN
- Aircraft age
- About 23 years (built 1997)
- 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
- Loss of control in flight
- 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
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The uncertificated pilot stated that he replaced the wing and control surface skins of the airplane and planned to perform a test flight. He said that shortly after adding power, the airplane "jumped up" 15 ft off the ground and drifted away from the runway centerline. The pilot applied corrective control inputs to return the airplane back to runway centerline and then applied full engine power to initiate a go-around. About 100 ft agl, the airplane banked hard to the left. The pilot applied right aileron control input but was unable to reduce the bank. The airplane descended and impacted the ground about 200 yards from the end of the runway. The pilot stated that there were no engine-related mechanical anomalies. The flight controls were subject to impact damage; however, the damage was consistent with failures associated with overload due to ground impact and not a failure in flight.
Probable cause
The uncertificated pilot's failure to maintain aircraft control during takeoff, which resulted in an impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA177
- Event ID
- 20200507X80348
- Case number
- CEN20CA177
- 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: 29b24c547542b3a87e9f1766a375332bf16d612e099da0e82eb8c0e6bbe4738e; retrieved 2026-09-16T11:34:06.817Z.