CESSNA 310F near Orange, MA — 2011-01-01
- Date
- 2011-01-01
- Location
- Orange, MA, USA
- Airport
- ORE
- Aircraft
- CESSNA 310F
- Registration
- N6725X
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 1
- Phase of flight
- Approach
Probable cause
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.
Contributing factors
Contributing to the accident was the pilot’s inadequate preflight planning and lack of recent night flight experience.
NTSB narrative
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.
Analysis
- Primary failure mode
- Human factors
- First missed decision gate
- Pilot should have aborted the approach due to low visibility and haze.
NTSB coding
Evidence available
- Photos
- 19 docket documents
Docket documents19
- Miscellaneous: Public Information for the Orange Municiple Airport.form
- Other Pertinent Forms and Reports: Airport Light Inspection Results.form
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Retention / Release of Wreckage Formform
- Pilot's Interview by the Massachusetts State Police.interview
- Statement of Party Representatives to NTSB Investigationinterview
- Witness Statementsinterview
- Miscellaneous: Location of Acident Site to Airport.other
- Miscellaneous: METARS for Orange Municiple Airport for January 1, 2011.other
- Miscellaneous: Moon's Position on the Day of the Accident.other
- Records of Conversation with NTSB.other
- Records of Conversation.other
- Photo 1) Location of the Accident on an Aero Photo of the Airport.photos
- Photo 2) View of the Approach end of Runway 19. Note the Damaged Trees Behind the Airport Property; Centered to the Runway Center Line.photos
- Photo 3) View of the Airplane Among the Trees.photos
- Photo 4) View of the Wreckage Looking Forward From the Right Aft Section of the Airplane.photos
- Photo 5) An Overall View of the Wreckage Site Noting the Airport Property Fence in the Background. Photo Provided by the Cessna Aircraft Company.photos
- Photo 6) Closeup View of the Airplane Wreckage, Viewing the Left Side of the Airplane.photos
- Photo 7) View of the Wreckage on the Night of the Accident. Photo Provided by the Massachusetts State Police.photos
Related mishaps
- AMERICAN GENERAL ACFT CORP AG5B
2026-01-15 · Fairfield, NJ
- CUB CRAFTERS CCX-2000
2024-02-19 · Laotto, IN
- PIPER PA-32R-301T
2023-01-01 · Old Bridge, NJ
- PIPER PA-18-150
2022-07-27 · Kenai, AK
- PIPER PA-32-300
2022-05-27 · Princeton, MN
- Mini-MAX 1600R Sport
2021-12-13 · South Bend, IN