UNK64X1943

NTSB accident investigation · Beechcraft 23 · Lobos Island, PR · May 24, 1964

Accident · No injuriesClosed
Date
May 24, 1964
Place
Lobos Island, PR · LOBOS ISLAND, PR
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8733MBeechcraft 23
Status
Completed · report October 19, 1964
Report
Brief approved by the director
Case key
184102

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-1632  64/5/24    LOBOS ISLAND PR     BEECHCRAFT 23       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 685
        TIME - 1540                    N8733M              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 111 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LOBOS ISLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8733M
Reported as
Beechcraft 23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lobos Island

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.