BFO95FA033 · Piper PA-46-310P
Piper PA-46-310P · Accident: in flight collision with terrain/water during initial climb
From Cambridge Dorchester Airport (CGE) to Martin State Airport (MTN)
Event
- NTSB case
- BFO95FA033
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Piper PA-46-310P
- Aircraft type
- Piper PA-46
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N166CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cambridge Dorchester Airport (CGE)To Martin State Airport (MTN), MARTIN STATE, MD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE COLLIDED WITH TREES SHORTLY AFTER TAKEOFF AND CAME TO REST IN A CHURCH YARD. THERE WERE NO WITNESSES TO THE CRASH; HOWEVER, SEVERAL LOCAL RESIDENTS HEARD THE AIRPLANE OVERFLY THEIR HOMES AT A LOW ALTITUDE. ONE RESIDENT STATED THAT HE HEARD THE AIRPLANE COLLIDE WITH THE TREES. ANOTHER RESIDENT STATED THAT HE HEARD THE ENGINE OPERATING AS THE AIRPLANE FLEW LOW OVERHEAD. BOTH RESIDENTS REPORTED THAT REDUCED VISIBILITY HAMPERED THEIR ABILITY TO FIND THE WRECKAGE. ONE RESIDENT ESTIMATED THAT THE VISIBILITY WAS ABOUT 50 TO 60 FEET. THE PRESCRIBED TAKEOFF MINIMUMS FOR THAT AIRPORT IS 300 FEET AND 1 MILE VISIBILITY. EXAMINATION OF THE AIRPLANE DID NOT DISCLOSE EVIDENCE OF MECHANICAL MALFUNCTION.
Probable cause
the commercial/instrument rated pilot's failure to obtain/maintain adequate altitude/clearance during the initial climb after takeoff. Related factors are the pilot's poor planning/decision making, and the fog.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO95FA033
- Event ID
- 20001207X03078
- Case number
- BFO95FA033
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 362276a0ac017f9c7dd2574e91991fa39590ff1a45d7adea01c90fbde9e1b503; retrieved 2026-09-20T23:50:56.593Z.