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

Cessna 182 accident near Ephraim, Wisconsin, September 19, 2016

On September 19, 2016 at about 1:31 am local time, a 2006 Cessna 182, registered N2012F, was destroyed in an accident during approach near Ephraim, Wisconsin (Ephraim-Gibraltar airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper decision to execute a maneuvering approach at low altitude during night conditions, which resulted in controlled flight into terrain.

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

What the record shows

Date
September 19, 2016 · about 1:31 am local time · cases in 2016
Place
Ephraim, Wisconsin · Ephraim-Gibraltar · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 182 T, built 2006 · all 182s on the register
Registration
N2012F · registry record · serial 18281769
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot was flying a passenger, who was a student pilot, home after her completion of a lesson with a flight instructor. During the night arrival to a nontowered airport, the pilot descended to about 150 ft above the ground on an extended right base to the runway. He subsequently flew across the runway's final approach course and began a left turn away from the runway, which continued for about 300° until impact with 50-ft-tall trees.      Although adequate visibility and moon illumination existed for a night visual approach, the runway's final approach was over an unpopulated state park surrounded by water on three sides with little cultural lighting. The lack of visual cues over this dark area likely contributed to the pilot perceiving his altitude to be higher than it was. Additionally, when the pilot turned left toward the dark area, he turned the airplane away from the runway's visual glideslope indicator, which could have provided the pilot with information about his height above the terrain. Further, the low altitude at which the pilot approached the airport and subsequently initiated his maneuvering to align with the runway did not allow for any imprecision in altitude control. It is unlikely that the pilot's diabetes, high blood pressure, or medications used to treat these conditions impaired the pilot or contributed to the accident. Additionally, there is no evidence the pilot's coronary artery disease or bilateral cataracts impaired the pilot or contributed to the accident.

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. Course deviation during approach (VFR pattern base)
  2. Controlled flight into terrain or object (CFIT) during approach defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Decision related to condition
  • cause Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 920 hours in all; 300 in this make and model
  • Last flight review: December 14, 2014
  • Medical certificate: Class 3 (waiver time limited special)
  • Seat: left
  • Injury: fatal

Dual student

  • Certificate: student
  • Medical certificate: None
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 3,426 hours
  • Last inspection: 100-hour inspection, September 8, 2016
  • Maximum gross weight: 2,348 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-540-AB1A5 (piston); 3,426 hours total
  • Fire on the ground
  • Operator: Keller Aviation LLC

The flight

  • Departed from: GRB Green Bay WI at 1:03 am
  • Destination: 3D2 Ephraim WI
  • Flight plan: IFR
  • Runway 14, 2,697 ft by 60 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 190° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 63°F (17°C), dew point 59°F (15°C)
  • Altimeter: 29.90 inHg
  • Observation at 1:35 am from 3D2, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

11 documents, released by the NTSB on June 14, 2018. 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/CEN16FA373.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.