ERA24LA208 · Admore International Jets LLC AIRCAM
Admore International Jets LLC AIRCAM · Accident: system/component malfunction/failure (non-power) on approach
From Spruce Creek Airport (7FL6) to an unrecorded destination
Event
- NTSB case
- ERA24LA208
- 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
- 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
Admore International Jets LLC AIRCAM
- Aircraft type
- Admore International Jets AIRCAM
- 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
- N848HP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), Daytona Beach, FLTo not recorded
- Aircraft age
- About 1 year (built 2023)
- 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
- Approach · VFR pattern base
- 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
- System/component malfunction/failure (non-power)
- 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 propeller/rotor
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot proceeded toward the destination airport in the experimental, amateur-built, twin-engine airplane that was equipped with a customized propeller pitch control system consisting of a standard electronically controlled propeller pitch device, plus various selectors and other limit switches, enabling the propellers to provide reverse thrust capability. After reducing power while on a base leg of the airport traffic pattern with both engines operating within about 30 rpm of each other, the pilot believed the propeller for the right engine went uncommanded into reverse. He said that he had not moved the propeller control guarded switches (which would have been one of several steps required to command the propeller to reverse) and that he did not see any propeller mode light illuminate on the instrument panel. Within 1 to 3 seconds, the airplane was uncontrollable and entered a spin, which, according to a witness, was to the left, and the airplane quickly lost altitude and impacted the ground.
Based on recorded data for various airplane parameters, about the time and location where the pilot likely reduced power, the left engine’s speed increased within 1 second from 4,630 rpm to about 5,330 rpm, consistent with propeller blade angle decreasing toward fine or low pitch, while the right engine’s speed remained about 4,660 rpm to 4,680 rpm. During the next 21 seconds, the left engine’s speed decreased and remained below 3,360 rpm, while the right engine’s speed increased to a maximum of 5,370 rpm, consistent with the maximum value recorded at takeoff.
During that time, the airplane rolled left briefly before rolling to and remaining in a right roll, the maximum extent of which was about 8°. During the next 13 seconds (to the end of the recorded data), the airplane’s indicated airspeed decreased to the lowest value of 47 kts, the left engine rpm values increased slightly while the right engine rpm decreased then stabilized, with both engines ending within 90 rpm of each other. The airplane’s bank angle values and directions changed, continuing in a left bank that increased during the last 4 seconds of the recorded data.
Postaccident examination of the wreckage revealed that the left propeller actuator was retracted, consistent with the propeller being in reverse, which matched the position of the left propeller blades, and the right propeller actuator was extended, consistent with the propeller being in cruise, which matched the position of the right propeller blades. Both propeller control guarded switches were found closed, consistent with the pilot’s statement.
Thus, based on the engine data parameters and the wreckage evidence, when the pilot reduced the throttles in preparation for landing, the variable-pitch left propeller moved uncommanded to, and likely past, the fine or low pitch position into reverse range. The reason for the uncommanded pitch change was not determined.
Although the pilot mistakenly perceived that the issue was with the right propeller and responded by applying left rudder (which would have exacerbated a spin to the left), given the airplane’s low altitude, the pilot had little time to assess and address the condition and likely could not have successfully regained control of the airplane before the airplane impacted the ground.
Probable cause
The uncommanded movement of the left propeller into reverse during approach for undetermined reasons, resulting in an in-flight loss of control of the airplane at low altitude during approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA208
- Event ID
- 20240503194200
- Case number
- ERA24LA208
- 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, 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: 120209dc85ae51713bfa5b8c0a728364e1a61bca8508ffa8046d0f4e0bb3c141; retrieved 2026-09-16T18:43:46.714Z.