Mightyfly INC MF-100 accident near Atwater, California, March 2, 2026
On March 2, 2026 at about 9:57 pm local time, a 2023 Mightyfly INC MF-100, registered N258MF, was destroyed in an accident during takeoff near Atwater, California (Castle airport). It was a flight test under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 2, 2026 · about 9:57 pm local time · cases in 2026
- Place
- Atwater, California · Castle · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Mightyfly INC MF-100, built 2023
- Registration
- N258MF · registry record · serial 0003
- Damage
- Destroyed
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Miscellaneous/other during takeoff defining event
- Loss of engine power (total) during takeoff
- Loss of control in flight during takeoff
The NTSB's findings
- Aircraft › Aircraft systems › Flight control system › (general) › Malfunction other cases naming the flight controls
- Aircraft › Aircraft power plant › Power plant › (general) › Capability exceeded other cases naming the engine
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
- Aircraft › Aircraft power plant › Power plant › (general) › Failure other cases naming the engine
Pilot
- Certificate: flight instructor, commercial pilot, private
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane; rotorcraft: unmanned (suas)
- Flight time: 459 hours in all; 0.5 in this make and model
- Last flight review: August 8, 2024
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: none
- Injury: no injuries
The aircraft
- Airframe total time: 3.7 hours
- Last inspection: continuous airworthiness programme, February 26, 2026; 0.5 hours since
- Maximum gross weight: 550 lb
- Seats: 0
- Landing gear: fixed
- Engine 1: Mightyfly (electric); 0 hours total
- Engine 2: Mightyfly (turbojet); 0 hours total
- Engine 3: Mightyfly (electric); 0 hours total
- Engine 4: Mightyfly (electric); 0 hours total
- Engine 5: Mightyfly (electric); 0 hours total
- Engine 6: Mightyfly (electric); 0 hours total
- Engine 7: Mightyfly (electric); 0 hours total
- Engine 8: Mightyfly (electric); 0 hours total
- Engine 9: Mightyfly (electric); 0 hours total
- Engine 10: Mightyfly (turbojet); 0 hours total
- Fire on the ground
- Operator: Mightyfly INC
The flight
- Departed from: MER Atwater CA at 9:54 pm
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 68°F (20°C), dew point 0°F (-18°C)
- Altimeter: 30.04 inHg
- Observation at 1:00 pm from MER, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on September 17, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Photos | PDF, 2 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N258MF on the register today · the tail number may have moved to another aircraft since
- Engine: Mightyfly · as the NTSB recorded it
- Engine: Mightyfly · as the NTSB recorded it
- Castle Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,098 in the last ten years
- California 27,686 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR26LA115.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.