FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA379 · McCaa Robert T AVID/KITFOX FLYER

28 Sept 2025 · Oakland, PA, United States

McCaa Robert T AVID/KITFOX FLYER · Accident: landing gear collapse

From John Murtha Johnstown Cambria County Airport (JST) to an unrecorded destination

Report a problem

Event

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

McCaa Robert T AVID/KITFOX FLYER

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
N533SE
Operator
Unknown
Onboard fatalities
Unknown
Route
From John Murtha Johnstown Cambria County Airport (JST), Johnstown, PATo not recorded
Aircraft age
About 10 years (built 2015)
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 · flare/touchdown
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
Landing gear collapse
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 › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The purpose of the flight was for the flight instructor to provide tailwheel training to the pilot receiving instruction, who did not hold an endorsement to flying tailwheel-equipped airplanes, and who had recently purchased the experimental amateur-built airplane. It was the first flight for either pilot in this make and model of airplane and the takeoff was performed by the pilot. The flight instructor stated that airplane’s acceleration was slower than he expected, but given his lack of experience in this airplane, he did not feel it was abnormal. When the airplane was about 50 ft above ground level, the pilot and flight instructor stated that the airplane stopped climbing. The pilots then elected to land on the remaining runway and the flight instructor took over controls, lowered the airplane’s nose, and reduced engine power. He noted that the airplane “dropped quick,” so he then increased the engine power. Upon touchdown, both landing gear collapsed, and the fuselage sustained substantial damage. The flight instructor further described that the airplane had touched down “hard,” but he was surprised that the landing gear had collapsed and that he landed other airplanes in the past with similar force and not experienced any problems. Prior to the flight, the pilot performed a weight and balance calculation and determined that the ramp weight would be 1,156 lbs, about 6 lbs above the airplane’s maximum demonstrated weight. The pilot stated that he expected that 6 lbs of fuel would be consumed during taxi and runup. Postaccident review of the weight and balance completed by the pilot revealed was based on the airplane’s original empty weight, which did not account for multiple propeller model changes, the addition of avionics, structural repairs, and a modification of the landing gear design. Additionally, the weather conditions at the time of the accident included a density altitude that exceeded 3,000 ft. Based on the Federal Aviation Administration Koch chart, this density altitude correlated to a loss in rate of climb performance of 35%. The flight instructor stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. The pilot also stated that there were no engine problems, but he reported that the experimental amateur-built airplane’s landing gear had been custom built and had not been designed by the airplane’s kit manufacturer. He also stated that the landing gear had previously collapsed and had been repaired by the previous owner/operator. A review of the airplane’s maintenance logs confirmed that the airplane had been damaged and repaired on at least three documented occasions. Given the uncertain nature of the airplane’s weight and balance, it is likely that the airplane was being operated near or in excess of its maximum gross weight during the accident takeoff. Combined with the detrimental performance impact of the density altitude at the time, it is likely that the airplane was unable to climb out of ground effect during the takeoff due to these combined factors. After aborting the takeoff, the flight instructor’s power management, in combination with the airplane’s excessive weight, resulted in a hard landing and the subsequent landing gear collapse. Whether the landing gear collapse was solely the result of that hard landing, or had been exacerbated by the landing gear’s design, or its previous damage and repair, was not determined.

Probable cause

The pilot/owner’s failure to accurately determine the airplane’s weight and performance limitations before initiating the takeoff. Contributing to the outcome was the flight instructor’s improper engine power management and landing flare, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA379
Event ID
20251010201831
Case number
ERA25LA379
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: ca423f9c5c4f8beede42535c2f9258a7ca6be2133290216f51058f43cf2812aa; retrieved 2026-09-16T20:27:19.965Z.