WPR26LA237 · Autogyro MT03
Autogyro MT03 · Accident: loss of engine power (total) during takeoff
Event
- NTSB case
- WPR26LA237
- 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
- Ongoing
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Autogyro MT03
- Aircraft type
- Autogyro MT03
- Category
- Gyroplane
- 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
- N423AG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 11 years (built 2015)
- 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 engine power (total)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On June 29, 2026, about 1148 Pacific daylight Time, a MTO Sport gyroplane, N423AG, was substantially damaged when it was involved in an accident at Reid-Hillview Airport (RHV), San Jose, California. The pilot was seriously injured, and the passenger received minor injuries. The gyroplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the purpose of the flight was to take a passenger on a local traffic pattern flight to demonstrate the gyroplane. The pilot reported that the pre-flight inspection, engine start, run-up, magneto check, and pre-takeoff checks revealed no anomalies. Before taking off from runway 14L, he engaged the secondary fuel pump. The pilot stated that the takeoff roll was normal; however, when the main landing gear was about 6 inches above the runway, the radio lost power. He attempted to reset the radio power but was unable to restore it, which he believed was indicative of a master power failure. As the gyroplane approached the departure end of the runway about 130 ft above ground level, the pilot noticed that the gyroplane was no longer climbing and had entered a slight descent. He selected a dirt area off the runway for a forced landing. The gyroplane continued to descend and impacted terrain at about 15 mph. Resulting in substantial damage to the fuselage and main rotor system. The wreckage was recovered to a secure location for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26LA237
- Event ID
- 20260630203283
- Case number
- WPR26LA237
- 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: e7ab3af25b71135af1331485c844357714bfc9722fb6bbdf8a19c14208a57a05; retrieved 2026-09-17T05:12:53.118Z.