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

Cessna 310F accident near Orange, Massachusetts, January 1, 2011

On January 1, 2011 at about 10:57 pm local time, a Cessna 310F, registered N6725X, was substantially damaged in an accident during approach (VFR pattern final) near Orange, Massachusetts (Orange Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot did not maintain separation from trees during landing. Contributing to the accident was the pilot’s inadequate preflight planning and lack of recent night flight experience.

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

What the record shows

Date
January 1, 2011 · about 10:57 pm local time · cases in 2011
Place
Orange, Massachusetts · Orange Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 310F · all 310Fs on the register
Registration
N6725X · no longer on the register · serial 310-0025
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot and passenger were on a pleasure flight in the multi-engine airplane and at the last moment the pilot decided to conduct a touch-and-go landing and takeoff at a nearby airport. During a short final leg of the landing approach, the pilot recalled seeing white and red lights on the left side of the runway and believed these were visual approach slope indicator lights. He was uncertain of what light color arrangement indicated a proper glide path to the runway. As the airplane approached the runway, the lights started to flicker, at which time the pilot applied full engine power, but the airplane immediately collided with trees and came to rest inverted. The pilot stated that there was less ambient light than he had anticipated and that there was haze in the air. He was not aware of the trees at the approach end of the runway. The airport was not tower controlled and none of the 4 runways were equipped with visual approach slope indicator lights. The intended landing runway has a published displaced threshold that is 850 feet from the runway’s original threshold. Published information cautions about trees at the approach end of that runway. The pilot did not review any publication for the intended airport before the flight. Additionally, the pilot did not hold a multi-engine rating or a multi-engine solo endorsement. The last entry in his flight logbooks for night flight was in 2000. The pilot reported no mechanical issues with the airplane before 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. Altitude deviation during approach (VFR pattern final)
  2. Controlled flight into terrain or object (CFIT) during approach (VFR pattern final) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › (general) › (general) › Pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Recent experience › Pilot
  • Environmental issues › Conditions/weather/phenomena › Light condition › Low light › Effect on personnel
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Haze/smoke › Effect on personnel
  • Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot
  • factor Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Pilot

Pilot

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

The aircraft

  • Airframe total time: 5,416 hours
  • Last inspection: annual inspection, February 1, 2010; 55 hours since
  • Maximum gross weight: 4,830 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine 1: Cont Motor IO-470 SERIES (piston); 0 hours total
  • Engine 2: Cont Motor I0-470 SERIES (piston); 0 hours total

The flight

  • Departed from: EEN Keene NH at 9:30 pm
  • Destination: EEN Keene NH
  • Flight plan: none
  • Runway 19, 5,000 ft by 75 ft

Weather at the time

  • Light: night
  • Wind: from 310° at 3 knots
  • Visibility: 9 statute miles
  • Sky: clear
  • Temperature: 36°F (2°C), dew point 34°F (1°C)
  • Altimeter: 30.00 inHg
  • Observation at 10:52 pm from ORE

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

19 documents, released by the NTSB on December 21, 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, 1 page View Download
2 Witness Statements PDF, 5 pages View Download
3 Pilot's Interview by the Massachusetts State Police. PDF, 4 pages View Download
4 Records of Conversation. PDF, 6 pages View Download
5 Records of Conversation with NTSB. PDF, 2 pages View Download
6 Other Pertinent Forms and Reports: Airport Light Inspection Results. PDF, 3 pages View Download
7 Miscellaneous: Public Information for the Orange Municiple Airport. PDF, 4 pages View Download
8 Miscellaneous: Metars for Orange Municiple Airport for January 1, 2011. PDF, 1 page View Download
9 Miscellaneous: Moon's Position on the Day of the Accident. PDF, 4 pages View Download
10 Miscellaneous: Location of Acident Site to Airport. PDF, 1 page View Download
11 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
12 Retention / Release of Wreckage Form PDF, 2 pages View Download
13 Photo 1) Location of the Accident on an Aero Photo of the Airport. PDF, 1 page View Download
14 Photo 2) View of the Approach End of Runway 19. Note the Damaged Trees Behind the Airport Property; Centered to the Runway Center Line. PDF, 1 page View Download
15 Photo 3) View of the Airplane Among the Trees. PDF, 1 page View Download
16 Photo 4) View of the Wreckage Looking Forward from the Right Aft Section of the Airplane. PDF, 1 page View Download
17 Photo 5) an Overall View of the Wreckage Site Noting the Airport Property Fence in the Background. Photo Provided by the Cessna Aircraft Company. PDF, 1 page View Download
18 Photo 6) Closeup View of the Airplane Wreckage, Viewing the Left Side of the Airplane. PDF, 1 page View Download
19 Photo 7) View of the Wreckage on the Night of the Accident. Photo Provided by the Massachusetts State Police. 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/ERA11FA102.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.