FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA388 · Cessna 172

30 Aug 2013 · Limington, ME, United States

Cessna 172 · Accident: loss of control in flight during takeoff

From Limington Harmon Airport (63B) to Limington Harmon Airport (63B)

Report a problem

Event

NTSB case
ERA13FA388
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
1 · 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

Cessna 172

Aircraft type
Cessna 172
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
N8063B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Limington Harmon Airport (63B), Limington, METo Limington Harmon Airport (63B), Limington, ME
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
Takeoff
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
Loss of control in flight
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

  • Personnel issues › Physical

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

NTSB narrative

The 58-year-old student pilot attempted a takeoff in light wind, but about 2,000 feet down the runway, he lost control of the airplane. Only one witness saw the airplane after liftoff, and noted that it was "swerving all over the place before it crashed." While airborne, the airplane veered off the left side of the runway, then impacted the ground with the right wing tip, nosed down, bounced, and came to rest upright, facing opposite the direction of takeoff. All witnesses heard the engine operating throughout the event, with one stating that it "was running smooth, normal sounding." Subsequent examination of the airplane revealed no preexisting mechanical anomalies that would have precluded normal operation.

The pilot was obese, with a history of Type 2 diabetes and high cholesterol. Although he reported some medications on his Federal Aviation Administration (FAA) medical certificate applications, he routinely failed to report others. Documentation from his most recent FAA medical examination included the use of two medications not recommended to be used together because of the risk of hypoglycemia. Postmortem toxicology testing identified only salicylate, but would have been unable to identify many of the pilot's other medications.

According to the medical examiner, the cause of death was multiple blunt impact trauma to the head and chest, indicating that the pilot was still alive when he lost control of the airplane. Diabetics who become symptomatic from hypoglycemia may not notice warning signs until their psychomotor functioning is very impaired. It is unknown what precautions the pilot may have taken that day to prevent hypoglycemia or what the pilot's eating schedule was. In addition, because postmortem glucose levels are low and do not correlate with premortem levels, even if the pilot was severely hypoglycemic at the time of the accident, there would be no specific evidence to identify it.

The pilot also had severe coronary artery disease, with 85-95% occlusion of the left anterior descending artery, that put him at increased risk of a sudden, impairing cardiac event that would have left no observable evidence at autopsy.

There were no operational or mechanical factors to explain the student pilot's loss of control at takeoff, but he did have multiple medical conditions that could have resulted in acute impairment without leaving evidence. Although the exact mechanism could not be determined, it is likely that the impairment resulted from one or more of the student pilot's medical conditions, which then caused him to lose control of the airplane.

Probable cause

An impairing medical event of undetermined origin that led to a loss of control during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA388
Event ID
20130830X25845
Case number
ERA13FA388
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. 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: 8678946544493c80b648badef8c5e082f0dc28c56d1c5e6ffd1bae3407968370; retrieved 2026-09-14T16:03:21.442Z.