- Date
- May 15, 1975
- Place
- Salisbury, MD · SALISBURY, MD
- Injuries
- 1 fatal, 4 serious
- Damage
- Destroyed
- Phase of flight
- Initial climb
- Aircraft
- N23XYBeech E18S
- Status
- Completed · report August 19, 1975
- Report
- Brief approved by the director
- FAA report
- 19750515022119A
- Case key
- 149181
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-2103 75/5/15 SALISBURY,MD BEECH E18S CR- 0 1 0 NONCOMMERCIAL COMMERCIAL, AGE 52, 2395 TIME - 0007 N23XY PX- 1 3 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 85 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - SALISBURY DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP SALISBURY,MD HAITI FORT LAUDERDALE,FL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB STALL: MUSH TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS PILOT IN COMMAND - FAILED TO FOLLOW APPROVED PROCEDURES,DIRECTIVES,ETC. PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - IMPROPERLY LOADED AIRCRAFT-WEIGHT-AND/OR C.G. PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- DID NOT USE FUEL BOOST PUMPS FOR TKOF.ACFT ABT 400LB OVR G/W.
Aircraft
- Registration
- N23XY
- Reported as
- Beech E18S
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Salisbury
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.