Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

February 12, 2011 · Piper PA-28-161 · N536PU

Minneapolis, MN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 12, 2011
Injury Outcomes
No injuries (3 uninjured)
Location
Minneapolis, MN
Aircraft
Piper PA-28-161
Tail Number
N536PU
Operator
Metro Aircraft
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN11LA183

The pilot reported that the airplane’s engine started to run rough upon takeoff and that he had trouble gaining altitude. He returned to the airport and performed a landing with the rough-running engine. After landing, the airplane veered to the left, the main landing gear impacted a snowbank, and the airplane impacted a runway light. A postaccident examination of the wreckage did not reveal any preimpact anomalies with the airframe. According to the operator, the accident engine was torn down and no anomalies were found. The airport's temperature and dew point were plotted on a carburetor icing chart and their intersection fell in the “serious icing (cruise power)” range.

NTSB Probable Cause

Environmental issues-Conditions/weather/phenomena-Temp/humidity/pressure-Conducive to carburetor icing-Contributed to outcome - F

Full Narrative

On February 12, 2011, about 1400 central standard time, a Piper PA-28-161 single-engine airplane, N536PU, sustained substantial damage when it exited the runway and impacted snow and terrain during a precautionary landing on runway 14L (3,263 feet by 75 feet, asphalt) at the Crystal Airport (MIC), near Minneapolis, Minnesota. The pilot reported that the airplane had a rough running engine during climbout and circled around for the precautionary landing. The pilot and two passengers were not injured. Visual meteorological conditions prevailed, and no flight plan was on file for the 14 Code of Federal Regulations Part 91 personal flight. The local flight had departed from MIC about 1350. The pilot reported that the airplane’s engine started to run rough upon takeoff and that he had trouble gaining altitude. He performed the checklist for engine power loss and his switching fuel tanks did not make a difference in the engine roughness. He stated that he reduced the throttle “slightly” and the engine increased its power. The engine began to run rough again and he called the tower for a landing clearance. He was given a clearance and performed a “standard landing procedure.” After landing the airplane veered to the left and the main landing gear impacted a snowbank and snow. The airplane impacted a runway light. The right wing sustained substantial damage on impact with the snowbank. A Federal Aviation Administration inspector examined and took pictures of the wreckage. The examination and review of the pictures did not reveal any airframe preimpact anomalies. According to the operator, the accident engine was torn down and no anomalies were detected. At 1253, the recorded weather at MIC was: Wind 190 degrees at 7 knots; visibility 10 statute miles; sky condition scattered 5,500 feet, overcast 7,500 feet; temperature 2 degrees C; dew point -3 degrees C; altimeter 29.80 inches of mercury. The airport's temperature and dew point were plotted on the carburetor icing chart listed in Special Airworthiness Information Bulletin CE-09-35. Their intersection fell in the “serious icing (cruise power)” range.

Flight

Event TypeAccident
Event Time14:00 CST
Nearest AirportCrystal Airport (0nm)
Runway14L
Runway Length3263 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-161
Tail NumberN536PU
Aircraft CategoryAir
DamageSubstantial
OperatorMetro Aircraft
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D3G · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 37 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind190° @ 7 kt
Visibility10 sm
CeilingOvercast 7600 ft
Temperature / Dew Point36 C / 27 C
Altimeter29.79 inHg
Observation Time18:53
Weather SourceWFAC

Appendix: Source Data