ERA25LA337 · Larocca Roch B ERACER MK II
Larocca Roch B ERACER MK II · Accident: system/component malfunction/failure (non-power) during landing
From Peachtree City Falcon Field (FFC) to an unrecorded destination
Event
- NTSB case
- ERA25LA337
- 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
Larocca Roch B ERACER MK II
- Aircraft type
- Larocca Roch ERACER MK
- 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
- N382RB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Peachtree City Falcon Field (FFC), Peachtree City, GATo not recorded
- Aircraft age
- About 13 years (built 2012)
- 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
- Landing · landing roll
- 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 structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot experimental amateur-built airplane reported that the approach and landing were normal with no anomalies observed. During the landing roll, the airplane’s retractable nose landing gear collapsed, and the airplane veered off the runway before it impacted uneven terrain. The airplane’s right wing was substantially damaged during the accident sequence. Postaccident examination of the airplane revealed that the nose landing gear actuator bolt had failed, which likely resulted in the collapse of the nose gear assembly during the landing.
Probable cause
The failure of the nose gear actuator bolt during the landing roll, which resulted in the collapse of the nose landing gear and subsequent runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA337
- Event ID
- 20250910200973
- Case number
- ERA25LA337
- 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: d8722c4230770dbe8f773e2ccee116d9d7276cbd6b16c4b75b06cf74f1164da4; retrieved 2026-09-16T20:19:23.593Z.