CEN26FA109 · Robert G Elves TARRAGON (TARR)
Robert G Elves TARRAGON (TARR) · Accident: loss of engine power (total) en route
From Stellar Airpark (P19) to an unrecorded destination
Event
- NTSB case
- CEN26FA109
- 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
- 1 · 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
Robert G Elves TARRAGON (TARR)
- Aircraft type
- Robert G Elves TARRAGON
- 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
- N35RR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stellar Airpark (P19), Chandler, AZTo not recorded
- Aircraft age
- About 4 years (built 2022)
- 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
- 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 February 6, 2026, at 1532 mountain standard time, a Tarragon airplane, N35RR, was substantially damaged when it was involved in an accident near Shawmut, Arizona. The pilot was fatally injured and the passenger received serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. According to flight track data downloaded from the airplane’s on-board avionics suite, the airplane departed from the Stellar Airpark (P19), Chandler, Arizona, about 1439. The airplane then flew south-southwest about 26 nautical miles (nm) where it turned to a west heading. The airplane then flew about 26 nm west where the data indicated that a full stop landing was made at the Gila Bend Municipal Airport (E63), Gila Bend, Arizona, with an immediate taxi back to the departure runway. After the subsequent takeoff from E63, the airplane headed east about 14 nm before it turned northeast and flew for about 1 nm, where the recorded data ended. The accident site was located about 2.4 nm north-northwest of the final recorded position.
Figure 1. Google Earth plot of the airplane’s flight path. The airplane was equipped with a Galaxy GRS Parachute Rescue System. The parachute was found deployed at the accident scene; however, the bonded-on panels covering the parachute harness straps along the fuselage sides had not separated from the airplane. Additionally, the rocket motor was found about 800 ft south of the main wreckage.
Figure 2. The accident airplane during the on-scene examination Examination of the airplane’s primary flight control system did not reveal any preimpact anomalies. The airplane’s landing gear was in the retracted position and the flaps were up. The propeller hub remained attached to the engine propeller flange. One blade remained attached to the hub. The other two blades were broken just outboard of the metal hub with a portion of each blade root retained in the hub. The propeller blades were of wood core construction with composite covering. All 3 propeller blades exhibited minimal damage, and the 2 separated blades were found in the immediate area of the accident site.
Figure 3. The airplane’s propeller during on-scene examination. Initial examination of the engine revealed that the propeller flange could only be rotated a few degrees. The No. 1 and No. 2 cylinders were removed which revealed that the end of the No. 2 connecting rod that attached to the crankshaft had failed.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN26FA109
- Event ID
- 20260207202405
- Case number
- CEN26FA109
- 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: f072913273771007a1894793b949f6d979c5133360f40fd12cab7318b98d3198; retrieved 2026-09-15T09:13:20.886Z.