FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA240 · Weatherly 201B

14 Jun 2015 · Pell City, AL, United States

Cobb Aerial Solutions Weatherly 201B · Accident: system/component malfunction/failure (non-power) during landing

From St Clair County Airport (PLR) to an unrecorded destination

Report a problem

Event

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

Weatherly 201B

Aircraft type
Weatherly 201
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
N1272W
Onboard fatalities
Unknown
Route
From St Clair County Airport (PLR), Pell City, ALTo not recorded
Aircraft age
About 41 years (built 1974)
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 137: Agricultural
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
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 systems
  • Personnel issues › Task performance

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

NTSB narrative

The pilot indicated that, while landing, everything appeared normal until he felt a “jolt” during the landing rollout. The right main landing gear collapsed, and the right wing struck the runway. He stated that the airplane then veered "violently" to the right, exited the right side of the runway, and came to rest in the grass. Upon egressing from the airplane, the pilot observed that the right main landing gear had completely separated from the airplane and was in the center of the runway, about 500 ft down the runway past his touchdown point. The airplane sustained substantial damage when the right main landing gear contacted the wing spar during the gear collapse. Examination of the right main landing gear assembly revealed that the assembly was fractured in four attachment locations. Flaking paint and oxidation of the metal surface indicate corrosion had occurred at the fracture locations. The main landing gear likely fractured due to corrosion fatigue at the upper inboard attachment point. Areas of fracture recontact were observed at the upper inboard fracture location, which indicate that it likely fractured before the other locations. Although this recontact could suggest a complete separation occurred before the accident flight, it is also possible that the separation occurred during the accident landing and that the recontact was the result of spring-back loads that occurred during the landing. The corrosion fatigue crack at the upper inboard attachment location initiated at the forward face of the attachment ear where it intersected the adjacent tube. The fracture surface at the upper outboard attachment had indications of fatigue cracks initiating at a similar intersection between the forward face of the ear and the tube. The fracture surfaces were substantially damaged in the fracture process, so the crack lengths before failure could not be determined; however, it is likely that fatigue cracks extended along most of the height of the ear and through the thickness of the forward plate at each upper attachment location. The sliding contact damage in the forward direction at the upper outboard attachment location combined with the bending deformation and overstress fracture at the lower attachment points also indicated that the fracture occurred at the upper attachment locations before the lower attachment locations. After separation at the upper attachment locations, the upper end displaced forward due to drag loads at the lower end, effectively rotating the assembly about the lower attachment locations, which resulted in secondary overstress fractures due to bending loads at the lower attachment points. Preexisting cracks were also observed on the lower sides of the lower attachments. However, the fracture surfaces for those areas were damaged because they were on the compression side of the fracture. The cracks did not contribute to the separation because they were on the compression side of a bending fracture. The airplane’s most recent annual inspection was completed 25 days before the accident. The poor condition of the landing gear should have been noticeable and detected because inspections for the landing gear should have included the lower side of the lower attachments as well as the entire upper attachment area and the areas where the ears intersected the tubes.

Probable cause

The inadequate inspection of the airplane's landing gear, which resulted in a collapse of the right main landing gear due to cracking and corrosion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA240
Event ID
20150616X50938
Case number
ERA15LA240
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: 8356ff0f73a84ac07f9f5630ba7b5596670477f13b8f8b5e2b867a5a06326824; retrieved 2026-09-16T02:25:46.477Z.