FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18TA236 · Cessna 182 L

27 Aug 2018 · Hanson, MA, United States

Cessna 182 L · Accident: runway excursion during landing

From Cranland Airport (28M) to Cranland Airport (28M)

Report a problem

Event

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

Cessna 182 L

Aircraft type
Cessna 182
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
N3115R
Onboard fatalities
Unknown
Route
From Cranland Airport (28M), Hanson, MATo Cranland Airport (28M), Hanson, MA
Aircraft age
About 50 years (built 1968)
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
Runway excursion
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 › 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 commercial pilot reported that during the airplane's initial climb for the local skydiving flight, the radio stopped working. He continued climbing to 7,500 ft to allow skydivers to depart the airplane, noted that the engine was running roughly at that time, then circled down over the airport. The pilot reported that his approach was "a little faster and higher than normal" and that he landed longer than usual but chose not to execute a go-around because of the rough-running engine. Surveillance video and witnesses indicated that the airplane touched down near the midpoint of the 1,760-ft-long runway with a quartering tailwind. The airplane's tires left over 500 ft of skid marks before the airplane overran the departure end of the runway, encountered a ditch, nosed over, and came to rest inverted 183 ft beyond the departure end of the runway.

Postaccident testing of the brakes showed that they were operational and did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. In addition, postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal engine operation, except that the alternator belt was found off of its pulleys. However, the airplane's battery still indicated a normal voltage, and the airplane's flaps were found extended, indicating that the airplane's electrical system was still functional throughout the landing attempt. Despite the condition of the alternator belt, the airplane's engine never ceased producing power. The pilot should have been able to perform a normal landing but instead performed a faster and higher approach than normal and failed to attain the proper touchdown point.

Probable cause

The pilot's failure to attain the proper touchdown point, which resulted in a runway overrun. Contributing to the accident was the pilot's decision to land with a quartering tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18TA236
Event ID
20180827X62403
Case number
ERA18TA236
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: b99a866b2528e121a4d82b484aba2c3ff8ae8ce93b48157968b27832837f7802; retrieved 2026-09-16T08:10:02.338Z.