WPR19FA161 · Lockwood AIRCAM
Lockwood AIRCAM · Accident: aircraft structural failure during takeoff
From Hemet Ryan Airport (HMT) to Hemet Ryan Airport (HMT)
Event
- NTSB case
- WPR19FA161
- 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
Lockwood AIRCAM
- Aircraft type
- Lockwood 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
- N123GN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hemet Ryan Airport (HMT), Hemet, CATo Hemet Ryan Airport (HMT), Hemet, CA
- Aircraft age
- About 2 years (built 2017)
- 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
- Aircraft structural 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
- Aircraft › Aircraft structures
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot, who was also the owner/builder of the experimental amateur-built kit airplane, was conducting his first test flight in the airplane after having received a special airworthiness certificate 1 week earlier from the Federal Aviation Administration, which allowed him to begin Phase 1 flight testing. On the morning of the accident, several of the pilot's friends and acquaintances gathered to watch his first flight. A video showed that during takeoff, as the airplane reached about 20 ft above ground level, the left wing folded upward. The airplane immediately rolled left and subsequently impacted the ground. Examination of the airplane revealed that the forward and rear left-wing lift struts remained connected to the wing but were not attached to the fuselage attachment fittings. Further examination revealed that the fittings on the fuselage were intact, and their corresponding bolt holes were undamaged; the bolts were present and secured to the lift struts with washers and nuts but had not been connected to the fuselage through the attachment fittings. The forward and rear right-wing strut were properly attached to the fuselage attachment fittings and the hardware was secure. Two friends assisted the pilot during the build process. One of them was an airframe and powerplant mechanic, and he reported that the left wing had been removed and reinstalled several times during the build process due to build errors. Each installation required that the attachment hardware be removed and reinstalled, which the pilot performed each time on his own. The mechanic reported that he periodically reminded the pilot to verify that the attachment hardware had been installed correctly, but he continued to find loose screws and nuts throughout the build process. The pilot likely attempted to install the lift struts on the fuselage after the wing's last reinstallation but failed to ensure that the left-wing lift strut bolts were secured to the fuselage attachment points through the attachment fittings. Although postaccident testing revealed that a correctly installed lift strut was closer to the fuselage along the attachment fitting than an incorrectly installed lift strut, the pilot did not detect the difference between the left and right wings. Postaccident examination of the airframe and engine did not reveal any other mechanical malfunctions or failures that would have precluded normal operation. Therefore, the pilot’s failure to properly attach the left wing to the fuselage likely led to its failure shortly after takeoff. A Federal Aviation Administration designated airworthiness representative (DAR) inspected the airplane 1 week before the accident and issued the pilot a special airworthiness certificate the same day as he was comfortable with the overall assembly. The DAR was not responsible for the final construction and assembly of the airplane as this was the responsibility of the builder.
Probable cause
The pilot/builder's improper installation of the left wing during the build process, which resulted in the wing failing during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA161
- Event ID
- 20190608X53318
- Case number
- WPR19FA161
- 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: ee2f765de9a9ff416f4d42de33413079fb2ccdc38a755f8ec566f858d770f807; retrieved 2026-09-15T06:59:36.094Z.