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

Piper PA-28-181 accident near Great Barrington, Massachusetts, June 28, 2010

On June 28, 2010 at about 4:30 am local time, a Piper PA-28-181, registered N30062, was substantially damaged in an accident during approach (VFR pattern base) near Great Barrington, Massachusetts (Walter J Koladza Airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's attempted visual flight into night instrument meteorological conditions, which resulted in spatial disorientation and subsequent 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
June 28, 2010 · about 4:30 am local time · cases in 2010
Place
Great Barrington, Massachusetts · Walter J Koladza Airport · cases near this airport · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-28-181 · all PA-28-181s on the register
Registration
N30062 · no longer on the register · serial 28-7990081
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

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.

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

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Fog › Effect on operation
  • cause Personnel issues › Psychological › Perception/orientation/illusio › Spatial disorientation › Pilot

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 550 hours in all; 216 in this make and model; 55 in the last 90 days; 31 in the last 30 days; 459 as pilot in command
  • Last flight review: June 17, 2010
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 5,210 hours
  • Last inspection: annual inspection, June 2, 2010
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O&VO-360 SER (piston); 0 hours total
  • Operator: Berkshire Aviation Enterprises INC

The flight

  • Departed from: 5B2 Saratoga Spring NY at 4:15 am
  • Destination: GBR Great Barrington MA
  • Flight plan: IFR
  • Runway 29, 2,579 ft by 50 ft

Weather at the time

  • Light: night, dark
  • Visibility: 0 statute miles
  • Sky: ovct at 100 ft
  • Temperature: 66°F (19°C), dew point 66°F (19°C)
  • Altimeter: 29.65 inHg
  • Observation at 4:54 am from PSF, 16 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

13 documents, released by the NTSB on June 13, 2011. 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 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Witness Statements PDF, 6 pages View Download
3 Weather Records: Kpsf Metars PDF, 2 pages View Download
4 Bershire Aviation Fueling Records PDF, 1 page View Download
5 Engine Log Excerpt PDF, 1 page View Download
6 Photograph #1 - Front View of Airplane Wreckage (FAA) PDF, 1 page View Download
7 Photograph #2 - Backside View of Separated Left Wing (FAA) PDF, 1 page View Download
8 Photograph #3 - View of Damage to the Left Side of the Airplane (FAA) PDF, 1 page View Download
9 Photograph #4 - View of Firewall Damage (FAA) PDF, 1 page View Download
10 Global Positioning System Device - Specialist's Factual Report PDF, 6 pages View Download
11 Global Positioning System Device - Attachment 1 (Csv Tabular Data) data file Download
12 Global Positioning System Device - Attachment 2 (Csv Tabular Data) data file Download
13 Post-accident Engine Run Video AVI file 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/ERA10CA337.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.