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

June 28, 2010 · Piper PA-28-181 · N30062

Great Barrington, MA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 28, 2010
Injury Outcomes
2 injuries (2 serious injuries)
Location
Great Barrington, MA
Aircraft
Piper PA-28-181
Tail Number
N30062
Operator
Berkshire Aviation Enterprises
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ERA10CA337

The pilot departed his home airport at night, in fog, and returned on an instrument flight rules (IFR) clearance. He stated that the return flight was routine and the air traffic controller cleared him for the approach into the airport. The pilot then canceled his IFR clearance, descended visually, and entered a left traffic pattern to land. The pilot stated that he entered the downwind leg for a "tighter than normal" pattern to avoid the fog at the approach end of the runway; however, global positioning system data revealed a spiraling descent in the vicinity of the base leg of the traffic pattern. The pilot stated that not seeing the terrain surrounding the airport while having the airport in sight lulled him into the belief that he was on or near glide path when, in fact, he was much lower, causing the controlled flight into terrain. The airplane incurred substantial damage to the left wing and left side of the fuselage. The pilot reported that there were no mechanical failures or malfunctions of the airplane. Airports 15 miles north and 10 miles west each reported ceilings less than 100 feet, and visibility less than a half mile, and witnesses surrounding the airport described the fog as heavy with visibility of less than 100 feet.

NTSB Probable Cause

The pilot's attempted visual flight into night instrument meteorological conditions, which resulted in spatial disorientation and subsequent controlled flight into terrain.

Full Narrative

The pilot departed his home airport at night, in foggy conditions, and returned on an instrument flight rules (IFR) clearance. He stated that the return flight was "routine" and was cleared for the NDB-A approach into the airport. The pilot then canceled his IFR clearance and descended the airplane visually. He stated he entered the downwind leg for a "tighter than normal pattern" to avoid the fog at the approach end of the runway, however, GPS data revealed a spiraling descent in the vicinity of the base leg of the traffic pattern. The pilot stated, "Again, everything was routine until the base leg...As I continued, with the runway and runway environment in sight, I suddenly felt an impact...Not seeing the terrain surrounding the airport while having the airport in sight, lulled me into the belief that I was on or near glide path when, in fact, I was much lower, causing the CFIT (controlled flight into terrain)." The airplane incurred substantial damage to the left wing and left side of the fuselage. The pilot reported that there were no mechanical failures or malfunctions of the airplane. Weather reported 15 miles north included a 100-foot ceiling and a half mile of visibility due to fog. Witnesses surrounding the accident airport described the fog as "heavy" with visibility "less than 100 feet."

Flight

Event TypeAccident
Event Time00:30 EDT
Nearest AirportWalter J Koladza Airport (1nm)
Runway29
Runway Length2579 ft
Runway Width50 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-181
Tail NumberN30062
Aircraft CategoryAir
DamageSubstantial
OperatorBerkshire Aviation Enterprises
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O&VO-360 SER · Reciprocating · 180
Seats4

People & Injuries

Injury Summary2 injuries (2 serious injuries)
Fatal0
Serious2
Minor0
Uninjured0
Total2
Crew 1Age 20 · Third Class · Serious

Conditions

ConditionsIMC
LightDark Night
WindCalm
Visibility0 sm
CeilingNone
Temperature / Dew Point66 F / 66 F
Altimeter29.65 inHg
Observation Time04:54
Weather SourceWFAC

Appendix: Source Data