WPR26LA236 · Beech S35
JCT Holdings Beech S35 · Accident: powerplant system/component malfunction/failure en route
From Eagle Roost Airpark (27AZ) to YKN · Yuma, AZ
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR26LA236
- 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
- Event fatalities
- Unknown
- 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
- Not recorded
Beech S35
- Aircraft type
- Beechcraft 35
- 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
- N6040F
- Operator
- JCT Holdings
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Eagle Roost Airpark (27AZ), Aguila, AZTo YKN · Yuma, AZ
- Aircraft age
- Not recorded
- 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
- En route · cruise
- 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
- Powerplant system/component malfunction/failure
- 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 25, 2026, about 1125 mountain standard time, a Beech S35, N6040F, sustained substantial damage when it was involved in an accident near Dome, Arizona. The pilot and three passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he departed Eagle Roost Airport (27AZ), Aguila, Arizona, for a cross-country flight to Yuma Marine Corps Air Station/Yuma International Airport (YNK), Yuma, Arizona. According to the pilot, about 15 nm northeast of YNK the engine began to run rough, so he enriched the mixture to smooth out the engine. The pilot then decided to perform a precautionary landing and landed the airplane on a dirt road with the landing gear retracted. Shortly after touchdown, the airplane veered right off the road and came to rest upright in a ditch. Subsequently, the right wing was substantially damaged. The airplane was recovered to a secure facility for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26LA236
- Event ID
- 20260630203282
- Case number
- WPR26LA236
- 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: 914cba30d80bd20ba9d4a4530c73aa5a8c98ba271f2f1e8861d085d906de8b4a; retrieved 2026-09-17T05:12:50.614Z.