The U.S. aircraft register, updated daily
Accidents · NTSB ERA13FA059 · Final report

Cessna 172N accident near Owls Head, Maine, November 16, 2012

On November 16, 2012 at about 9:45 pm local time, a Cessna 172N, registered N6142F, was substantially damaged in an accident during takeoff near Owls Head, Maine (Knox County Regional Airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The vehicle driver's failure to verify that the runway was not occupied by an airplane before crossing the runway, which resulted in the vehicle being struck by a departing airplane, and the pilot's continued takeoff with flight control damage, which subsequently resulted in an aerodynamic stall and spin at low altitude.

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

What the record shows

Date
November 16, 2012 · about 9:45 pm local time · cases in 2012
Place
Owls Head, Maine · Knox County Regional Airport · cases near this airport · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 172N · all 172Ns on the register
Registration
N6142F · no longer on the register · serial 17273155
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

Shortly after the end of civil twilight and during the departure roll with about liftoff speed, the airplane collided with a private ground vehicle that was crossing the runway, which resulted in the separation of the airplane's right elevator. The vehicle driver reported that he did not see the airplane until after the collision as it was attempting to gain altitude. Witnesses observed the airplane attempting to climb, drifting left of the runway, and then beginning a left turn. Witnesses then observed the airplane in "slow flight" and subsequently spinning until impact. Examination of the vehicle revealed impact marks on the left front fender consistent in size and shape with the airplane's right elevator. One light bulb from the vehicle's headlights was located, and examination of the light bulb revealed that the filament was stretched, which is consistent with the light being on at the time of the collision. The driver stated that he did not, nor was ever required to, have a yellow beacon on his vehicle. After the accident, the airport required airport beacons to be placed on the top most portion of the vehicle and to be operational both day and night while that vehicle operates on the ramp, taxiway, runway, or any other areas that an aircraft may operate. Examination of the airplane's wingtip light bulbs revealed that the filaments were stretched, indicating that the lights were on at the time of the accident. Examination of the beacon and navigation light bulbs did not reveal any information about their operational status at the time of the accident. It could not be determined if the driver or pilot announced their intentions over the airport common traffic advisory frequency. A handheld radio was located on the vehicle's dashboard; however, it was found in the "off" position. When the radio was placed in the "on" position and the correct frequency was set, the radio transmitted and received with no anomalies noted. Although the airplane was close to or perhaps past liftoff speed, the pilot likely could have stopped the airplane on the remaining 3,600-feet of paved runway following the impact with the vehicle. However, the pilot did not discontinue the takeoff.

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. Runway incursion veh/AC/person during takeoff defining event
  2. Collision during takeoff/land during takeoff
  3. Loss of control in flight during initial climb
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • factor Environmental issues › Conditions/weather/phenomena › Light condition › (general) › Contributed to outcome
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained
  • Environmental issues › Conditions/weather/phenomena › Light condition › (general) › Contributed to outcome
  • cause Personnel issues › Action/decision › Action › Lack of action › Airport personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 49 hours in all; 49 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 7,602 hours
  • Last inspection: annual inspection, December 4, 2011
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-H2AD (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: RKD Owls Head ME at 9:45 pm
  • Destination: BGR Bangor ME
  • Flight plan: none
  • Runway 31, 5,007 ft by 100 ft

Weather at the time

  • Light: night, dark
  • Wind: from 340° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 37°F (3°C), dew point 27°F (-3°C)
  • Altimeter: 30.30 inHg
  • Observation at 9:55 pm from RKD

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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

23 documents, released by the NTSB on April 1, 2014. 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.

#DocumentWhat it is
1 Written Statement by Vehicle Driver PDF, 1 page View Download
2 Rockland Maine Weather PDF, 2 pages View Download
3 Witness Written Statements PDF, 4 pages View Download
4 Airframe Maintenance Records [excerpt] PDF, 1 page View Download
5 Engine Maintenance Logbook (Excerpt) PDF, 1 page View Download
6 Propeller Maintenance Logbook [excerpt] PDF, 1 page View Download
7 Fuel Receipt PDF, 1 page View Download
8 Knox Airport Certification of Training for Drivers PDF, 1 page View Download
9 Knox County Airport Training for Drivers PDF, 4 pages View Download
10 Lockheed Martin Statement on Flight Plan PDF, 2 pages View Download
11 Statement of Party Representatives to NTSB Investigation - Cessna PDF, 14 pages View Download
12 U. S. Naval Observatory Sun and Moon Data PDF, 1 page View Download
13 Toxicological Report Pilot PDF, 1 page View Download
14 Toxicological Report - Passenger PDF, 1 page View Download
15 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
16 Photo 1: Runway Looking West PDF, 1 page View Download
17 Photo 2: Night View from Runway Threshold with Truck on Taxiway A with Runway Lights on PDF, 1 page View Download
18 Photo 3: Vehicle After Impact PDF, 1 page View Download
19 Photo 4: Impact Mark on Vehicle PDF, 1 page View Download
20 Photo 5: Right Elevator After Recovery from Runway PDF, 1 page View Download
21 Photo 6: Airplane at Rest PDF, 1 page View Download
22 Photo 7: Right Horizontal Stabilizer at Rest PDF, 1 page View Download
23 Photo 8: Propeller at Rest PDF, 1 page View Download

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/ERA13FA059.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.