WPR24FA227 · Fantasy Air SRO ALLEGRO 2007
Fantasy Air SRO ALLEGRO 2007 · Accident: loss of control in flight during initial climb
From Eureka, UT to an unrecorded destination
Event
- NTSB case
- WPR24FA227
- 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
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- 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
- Visual Meteorological Cond
Fantasy Air SRO ALLEGRO 2007
- Aircraft type
- Fantasy Air ALLEGRO 2007
- 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
- N969RC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eureka, UTTo not recorded
- Aircraft age
- About 17 years (built 2007)
- 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
- Initial climb
- 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 control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed from a local airport and proceeded to land on a road where, according to acquaintances, the pilot frequently landed to hike in the surrounding area. Flight track data show that the airplane departed from the road a little over an hour after landing and subsequently impacted terrain about a minute later. The wreckage was later located in a field adjacent to the road. A nearby landowner stated that airplanes occasionally land on the road, though he did not observe the airplane on the day of the accident, and noted that dust devils were a common occurrence in the area. The investigation could not determine whether the pilot obtained a weather briefing before the flight. Postaccident examination of the airframe and engine revealed no evidence of a preexisting mechanical malfunction or failure that would have precluded normal operation. However, a flight control locking device was found about 22 ft from the airplane's right wing, raising the possibility that the airplane departed with the control lock installed. The airplane’s co-owner reported that the accident pilot had a history of sometimes omitting the preflight inspection. It is possible that the pilot omitted a departure preflight inspection and left the flight control locking device in place. The pilot had severe cardiovascular disease that placed him at increased risk for an impairing or incapacitating cardiac event, including chest pain, arrhythmia, or myocardial infarction. Although the autopsy found no evidence of such an event, cardiac arrhythmias and other acute cardiac conditions may not leave definitive postmortem findings when they occur immediately before death. While a pacemaker may record arrhythmias, the autopsy report did not indicate that the pilot's pacemaker was interrogated to evaluate device function or detect arrhythmias. The autopsy and toxicology findings also suggested a likely history of heart failure, a condition commonly associated with fatigue; however, heart failure was not specifically documented in the available medical records. Toxicology testing detected citalopram, an antidepressant medication, in the pilot's system. Based on the available evidence, it could not be determined whether the pilot was experiencing impairment from an underlying condition, such as depression, or adverse effects associated with his unreported citalopram use. The presence of frequent localized wind events, commonly referred to as dust devils, may have influenced the pilot to expedite his departure during a perceived lull between wind events. In doing so, the pilot likely inadvertently omitted the removal of the airplane's flight control locking device. During the departure, any wind-induced displacement of the wing from a level attitude would have left the pilot with limited ability to correct roll deviations as the aircraft ascended. Compounding the situation was the pilot's underlying medical condition and associated propensity for a cardiac event, which may have further degraded his ability to respond effectively to the developing emergency.
Probable cause
The pilot’s failure to maintain airplane control during initial climb, which resulted in an in-flight upset and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA227
- Event ID
- 20240708194620
- Case number
- WPR24FA227
- 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, cause areas. 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: bcbaa91c558238b20342e1d1284432dcb84fb831a16db87054ae53ba1f67dd70; retrieved 2026-09-15T08:24:12.219Z.