- Date
- February 26, 1974
- Place
- San Diego, CA · SAN DIEGO, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N6277BAero Comdr 500
- Status
- Completed · report May 20, 1974
- Report
- Brief approved by the director
- FAA report
- 19740226004099A
- Case key
- 170226
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-0710 74/2/26 SAN DIEGO, CALIF AERO COMDR 500 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 58, 3220 TIME - 1833 N6277B PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 12 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - MONTGOMERY DEPARTURE POINT INTENDED DESTINATION SAN DIEGO, CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION GROUND-WATER LOOP-SWERVE LANDING: ROLL GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA MISCELLANEOUS ACTS,CONDITIONS - INTENTIONAL GROUND-WATER-LOOP-SWERVE MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE REMARKS- LND ON TAXIWAY,SWERVED INTNTLLY TO AVOID OTR ACFT.
Aircraft
- Registration
- N6277B
- Reported as
- Aero Comdr 500
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Montgomery
N6277BRegistered now · Aero Commander 500Airframe modelAero Commander 500Engine modelLycoming 0-540 series
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.