# Incident 20030118000939I: Beech 6580, San Carlos, CA, January 18, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 18, 2003, 10:17 local time
- Place: San Carlos, CA
- Airport: San Carlos Airport
- Damage: Minor damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 37.5119° N, 122.2495° W: Placed by OpenAirDocs at SAN CARLOS (SQL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.5119&lon=-122.2495&mi=10
- Aircraft: N7864D, a cancelled registration (https://openairdocs.org/deregistered/N7864D-2013-07-30) (OpenAirDocs)
- Registry model: Beech 65-80 (registry code 1152806, https://openairdocs.org/model/beech-65-80) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: BEECH 6580
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 8,000 total, 180 in this make and model, 40 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030118000939I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) APPROXIMATELY 3 MINUTES AFTER DEPARTURE N7864D EXPERIENCED A COMPLETE LOSS OF ELECTRICAL POWER. THE PILOT AND HIS SINGLE PASSENGER CIRCLED NEARBY THE SAN CARLOS AIRPORT (SQL) WHILE TROUBLESHOOTING THE PROBLEM. HAVING NOT RESOLVED THE PROBLEM, THE PILOT DECIDED TO DO AN EMERGENCY EXTENSION OF THE LANDING GEAR AND LAND AT SQL. AFTER TOUCH DOWN, THE GEAR WAS OBSERVED COLLAPSING IMMEDIATELY AND THE AIRCRAFT VEERING TO THE LEFT OF RUNWAY 30. THE AIRCRAFT CONTINUED TO SKID INTO THE INFIELD AND STRUCK A GUIDANCE SIGN AND 2 TAXI WAY LIGHTS. THE AIRCRAFT THEN SWERVED BACK TO THE RIGHT ACROSS "DELTO" INTERSECTION STRIKING 2 MORE TAXI WAY LIGHTS AND COMING TO REST CLOSE TO THE CENTER LINE OF RUNWAY 30.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.