eFlight
Accidents · NTSB ERA17LA307 · Final report

Cessna U206 accident near Harpswell, Maine, September 1, 2017

On September 1, 2017 at about 9:10 pm local time, a 1979 Cessna U206, registered N4615X, was substantially damaged in an accident during enroute (cruise) near Harpswell, Maine. It was a positioning flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to maintenance personnel's failure to apply proper torque to the cylinder flange nuts and through bolts, which resulted in shifting of the Nos. 1, 2, and 3 main bearings, loss of lubrication, and failure of the crankshaft.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 1, 2017 · about 9:10 pm local time · cases in 2017
Place
Harpswell, Maine · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna U206 G, built 1979 · all U206s on the register
Registration
N4615X · registry record · serial U20605513
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that, while en route to his destination, he heard a “loud bang,” followed by a complete loss of engine power. After determining that the airplane was not within gliding distance of the nearest airport, the pilot performed an off-airport landing, during which the airplane impacted a small drainage ditch, nosed over, and came to rest inverted, resulting in substantial damage. Disassembly of the engine revealed mechanical damage in multiple locations inside the crankcase. The No. 1 main bearings had shifted slightly out of the support and displayed deformation. The No. 2 main bearings displayed bearing shift signatures. One was missing, and the other had extruded out of the bearing support. Multiple pieces of the missing bearing were found in the oil sump. The No. 3 main bearings were intact and had moved in a clockwise direction when viewed from the back of the engine, had shifted slightly out of the support, and the oil passage holes were partially blocked. The crankshaft was fractured at the crankshaft cheek between the No. 2 main journal and the No. 2 connecting rod journal. The No. 2 connecting rod journal and connecting rod bearings displayed incipient signatures of lubrication distress. Review of the engine maintenance records revealed that, about 500 flight hours before the accident, all the cylinders had been replaced with overhauled cylinders and new pistons had been installed along with reconditioned lifters and seals. If a bearing shifts for any reason after removal of one or more cylinders, or during replacement of one or more cylinders, the oil holes in the bearing can become misaligned with the oil passages in the crankcase, partially cutting off the oil supply to the bearing. If the engine is then put back into service, the reduced oil supply to the bearing can cause increased heat and friction that can result in the bearing shifting more, further reducing its oil supply. Eventually, the bearing can shift enough to cause the oil supply to be cut off completely, resulting in a catastrophic failure. This is usually referred to as a "spun bearing." To prevent a spun bearing, the manufacturer specified a multiple-step torquing process for proper cylinder installation. The process required that the through bolt nuts be torqued on both sides of the engine, even if only one cylinder was being installed. The manufacturer warned that "failure to torque through bolt nuts on both sides of the engine can result in a loss of main bearing crush with main bearing shift and subsequent engine failure." Given the observed damage, it is likely that maintenance personnel did not apply sufficient torque to the cylinder flange nuts and through bolts during installation of the cylinders, which resulted in shifting of the Nos. 1, 2, and 3 main bearings, a loss of lubrication, and failure of the crankshaft.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (total) during enroute (cruise) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
  3. Nose over/nose down during landing (landing roll)
  4. Off-field or emergency landing during emergency descent

The NTSB's findings

  • Personnel issues › Task performance › Maintenance › Replacement › Maintenance personnel
  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Incorrect service/maintenance other cases naming the engine
  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Damaged/degraded other cases naming the engine

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instrument: airplane
  • Flight time: 2,400 hours in all; 800 in this make and model; 200 in the last 90 days; 50 in the last 30 days; 2,371 as pilot in command
  • Last flight review: May 20, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 7,359.1 hours
  • Last inspection: 100-hour inspection, August 28, 2017
  • Maximum gross weight: 3,600 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-520F (piston); 0 hours total
  • Operator: Waters Aero-Marine INC

The flight

  • Departed from: RKD Rockland ME at 8:45 pm
  • Destination: PWM Portland ME

Weather at the time

  • Light: daylight
  • Wind: at 6 knots, gusting 22
  • Visibility: 10 statute miles
  • Sky: a few clouds at 6,500 ft
  • Temperature: 63°F (17°C), dew point 34°F (1°C)
  • Altimeter: 29.95 inHg
  • Observation at 8:53 pm from IWI, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 20 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on November 3, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA17LA307.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.