FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA534 · Barrow ROSE PARRAKEET A4C

7 Sept 2013 · Castroville, TX, United States

Barrow ROSE PARRAKEET A4C · Accident: system/component malfunction/failure (non-power) during landing

From Castroville Municipal Airport (CVB) to Castroville Municipal Airport (CVB)

Report a problem

Event

NTSB case
CEN13LA534
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
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

Barrow ROSE PARRAKEET A4C

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
N1732
Onboard fatalities
Unknown
Route
From Castroville Municipal Airport (CVB), Castroville, TXTo Castroville Municipal Airport (CVB), Castroville, TX
Aircraft age
Not recorded
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 oper/perf/capability
  • Aircraft › Aircraft systems
  • 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 stated that, during the landing roll, the left main landing gear wheel fractured. The experimental-homebuilt airplane subsequently veered off the runway and flipped over. Postaccident examination of the fractured left main wheel revealed that the wheel failed due to overstress of the cast aluminum alloy; no evidence of preexisting cracks was observed. According to the pilot, the wheel had accrued only 11.4 hours since he had installed it, and it had about 15 cycles (landings) at the time of the accident. The wheels installed on the airplane were designed for ultralight aircraft that have an empty weight of less than 254 pounds. The accident airplane weighed about 954 pounds and would have required wheels with a higher loading capability.

Probable cause

The failure of the left main landing gear wheel on landing due to overstress, which resulted in the pilot’s loss of directional control. Contributing to the accident was the pilot's improper decision to install wheels with insufficient loading capacity for the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA534
Event ID
20130909X85712
Case number
CEN13LA534
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: cf685ebbbf19c1cf43f5c222b5879ef4721142b57f4268d9cead9e32d51ad0a4; retrieved 2026-09-15T22:48:48.304Z.