- Date
- February 26, 1968
- Place
- Gurabo, PR
- Injuries
- 4 fatal
- Damage
- Destroyed
- Phase of flight
- Uncontrolled descent
- Aircraft
- N9577YBeech 35-33
- Status
- Completed · report June 3, 1968
- Report
- Brief approved by the director
- Case key
- 111497
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-1007 68/2/26 GURABO,PR BEECH 35-33 CR- 1 0 0 NONCOMMERCIAL PRIVATE, AGE 35, 340 TIME - 2005 N9577Y PX- 3 0 0 BUSINESS TOTAL HOURS, 10 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS PILOT IN COMMAND - BECAME LOST/DISORIENTED PILOT IN COMMAND - SPATIAL DISORIENTATION WEATHER - RAIN WEATHER - LOW CEILING WEATHER BRIEFING - BRIEFED BY FLIGHT SERVICE PERSONNEL, BY RADIO WEATHER FORECAST - FORECAST SUBSTANTIALLY CORRECT SKY CONDITION CEILING AT ACCIDENT SITE UNKNOWN/NOT REPORTED 800 VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 3 MILES OR LESS RAIN SHOWERS OBSTRUCTIONS TO VISION AT ACCIDENT SITE TEMPERATURE-F NONE 70 WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 300 6 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN IFR NONE FIRE AFTER IMPACT REMARKS- NON-INST RATED.STRUCK MOUNTAIN.
Aircraft
- Registration
- N9577Y
- Reported as
- Beech 35-33
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.