# NTSB WPR26LA115: Mightyfly MF-100, N258MF, Atwater, CA, March 2, 2026

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Class 4 · Limited · Final report
- Date: March 2, 2026, 13:57 local (21:57 UTC)
- Place: Atwater, CA
- Coordinates: 37.3805, -120.56816
- Nearby events: https://openairdocs.org/map.md?lat=37.3805&lon=-120.5682&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Miscellaneous/other](https://openairdocs.org/ntsb-events/900)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report September 17, 2026
- Report: Approved by Office Director
- Investigation class: Class 4 - Basic report with no Prelim publish
- NTSB office: Western Pacific Region
- Parties: FAA FSDO
- NTSB case key (mKey): 202591
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR26LA115
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202591/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=202591
- Page: https://openairdocs.org/ntsb/WPR26LA115

## Probable cause

A control system anomaly, which resulted in the overload and failure of one of the propulsion motor systems during the transition from hover to forward flight.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Flight control system](https://openairdocs.org/ntsb-findings/01022700): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-findings/01022700/cases.md?model=0610195), [All aircraft, 65 cases](https://openairdocs.org/ntsb-findings/01022700/cases.md)
- [Power plant](https://openairdocs.org/ntsb-findings/01057100): Aircraft › Aircraft power plant · Capability exceeded (probable cause); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-findings/01057100/cases.md?model=0610195), [All aircraft, 198 cases](https://openairdocs.org/ntsb-findings/01057100/cases.md)
- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=0610195), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Power plant](https://openairdocs.org/ntsb-findings/01057100): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-findings/01057100/cases.md?model=0610195), [All aircraft, 198 cases](https://openairdocs.org/ntsb-findings/01057100/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Takeoff: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=0610195), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Takeoff: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=0610195), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md)
- [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Mightyfly MF-100, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=0610195), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)

## Analysis

According to the manufacturer/operator, the unmanned aircraft took off in light and variable winds for a test flight. After a nominal hover and entry into transition from vertical to forward flight, it experienced control and estimation anomalies. During the ensuing upset sequence, one of the motor pods failed due to high load, further limiting recovery capability. The aircraft departed controlled flight and impacted terrain on an adjacent taxiway. The aircraft was destroyed during the accident sequence, and there were no injuries or damage to property.

## Aircraft

- Registration: [N258MF](https://openairdocs.org/aircraft/N258MF), registered now, S/N 0003, built 2023 (OpenAirDocs)
- Reported make and model: MIGHTYFLY INC MF-100
- Registry model: [Mightyfly MF-100](https://openairdocs.org/model/mightyfly-mf-100) (registry code 0610195) (OpenAirDocs)
- Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs)
- Category: Unknown, unmanned
- Serial number: 0003
- Year built: 2023
- Airframe hours: 3.7
- Engines: MightyFly electric; MightyFly electric; MightyFly electric; MightyFly turbo jet; MightyFly electric; MightyFly electric; MightyFly electric; MightyFly electric; MightyFly turbo jet; MightyFly electric
- Damage: Destroyed
- Fire: On-Ground
- Flight: Flight test, Part 91
- Operator: Mightyfly Inc
- Registered owner: Mightyfly Inc
- Airworthiness certificate: Standard, Other; Special, Experimental (Special)
- Last inspection: Continuous airworthiness, February 26, 2026, 0.5 hours before
- Departed: MER, Atwater, CA
- Destination: Same as departure
- Airport: MER, Castle
- Equipment: Auto-pilot, Angle of attack indicator, ADS-B, Data recorder

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 38; injuries: none; flight instructor, commercial, private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review August 8, 2024; seat: none; flight hours: 459 total, 0.5 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 68 °F
- Altimeter: 30.04 inHg
- Observed at: MER, 0.68 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20260302001769A](https://openairdocs.org/incident/20260302001769A), Mar 2, 2026: Mightyfly Inc MF-100, Atwater, CA, Destroyed. On March 2, 2026, at approximately 13:57 PDT, the subject aircraft (UAS) was conducting an autonomous early-phase research and development test flight at…

## Docket (2 files)

The files NTSB released with the investigation on September 17, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=202591. 4.2 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20735205&FileExtension=pdf&FileName=r_6120_Redacted-Rel.pdf
- Photos (item 2, PDF, 2 pages, 1 photo, 494 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20735568&FileExtension=pdf&FileName=r_Photos-Rel.pdf

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.