# Accident 19990605021999A: Beech A36, Van Nuys, CA, June 5, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 5, 1999, 12:25 local time
- Place: Van Nuys, CA
- Airport: Van Nuys Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 34.1509° N, 118.5197° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.1509&lon=-118.5197&mi=10
- Aircraft: N126GL, registered now (https://openairdocs.org/aircraft/N126GL) (OpenAirDocs)
- Registry model: Beech A36 (registry code 1151604, https://openairdocs.org/model/beech-a36) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT IO520BA
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 200 total, 65 in this make and model, 17 in the last 90 days
- NTSB investigation: [NTSB LAX99LA219](https://openairdocs.org/ntsb/LAX99LA219) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990605021999A

## Narrative

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

ON JUNE 5, 1999, AT 1225 HOURS PACIFIC DAYLIGHT TIME, A BEECH A-36, N126GL, LANDED GEAR UP ON RUNWAY 16R AT THE VAN NUYS, CALIFORNIA, AIRPORT. THE AIRCRAFT, OPERATED UNDER 14 CFR PART 91, SUSTAINED SUBSTANTIAL DAMAGE.  THE PRIVATE PILOT/OWNER WAS NOT INJURED.  VISUAL METEOROLOGICAL CONDITIONS EXISTED FOR THE PERSONAL FLIGHT THAT HAD DEPARTED THE VAN NUYS AIRPORT AT AN UNKNOWN TIME WITH A STOP AT THE OXNARD, CALIFORNIA, AIRPORT.  THE FLIGHT WAS SCHEDULED TO TERMINATE AT THE VAN NUYS AIRPORT.  NO FLIGHT PLAN WAS FILED.  IN AN INTERVIEW WITH A FEDERAL AVIATION ADMINISTRATION (FAA) INSPECTOR, THE PILOT STATED THAT AFTER DEPARTING FROM OXNARD, NO DISCREPANCIES WERE NOTED UNTIL HE WAS OVER SIMI VALLEY AND LOST ALL OF HIS RADIOS.  HE STATED THAT HE LOWERED THE LANDING GEAR, BUT DID NOT RECEIVE A GEAR SAFE INDICATION LIGHT.  THE PILOT REPORTED THAT HE CONTINUED HIS FLIGHT TO VAN NUYS AND THEN CIRCLED WEST OF THE AIRPORT WAITING FOR A GREEN LIGHT FROM THE TOWER.  THE PILOT STATED THAT AFTER RECEIVING THE GREEN LIGHT INDICATION FROM THE TOWER, HE "THOUGHT THE LANDING GEAR WAS IN THE DOWN AND LOCKED POSITION."  HE ENTERED THE PATTERN AND LANDED ON UNLOCKED LANDING GEAR THAT RESULTED IN THE   LANDING GEAR COLLAPSING AFTER TOUCHDOWN. THE FAA INSPECTOR STATED THAT DURING THE INTERVIEW THE PILOT DID NOT MAKE REFERENCE TO THE PILOT'S OPERATING HANDBOOK FOR EMERGENCY PROCEDURES TO CIRCUMVENT THE ELECTRICAL PROBLEM, OR MANUAL EXTENSION OF THE LANDING GEAR. THE PILOT WAS INTERVIEWED BY THE AIRPORT POLICE AND STATED THAT HE LOST HIS NAVIGATIONAL SYSTEM AND THEN RADIO COMMUNICATIONS. HE REPORTED THAT HE ROCKED HIS WINGS BACK AND FORTH, WAS GIVEN A GREEN LIGHT FROM THE TOWER TO LAND, AND ASSUMED THAT THE LANDING GEAR WAS DOWN PRIOR TO THE ELECTRICAL FAILURE. AIR TRAFFIC CONTROL TOWER PERSONNEL REPORTED THAT THE ACCIDENT AIRCRAFT ENTERED THE TRAFFIC PATTERN FOR 16R ON A RIGHT BASE WITH NO RADIO COMMUNICATION.  TOWER PERSONNEL ATTEMPTED TO COMMUNICATE WITH THE ACCIDENT AIRCRAFT AND SUBSEQUENTLY FLASHED A GREEN LANDING LIGHT WHEN THE GEAR WAS OBSERVED DOWN AND IN PLACE.                                                                                                                                                                                                                                                                                                                              (-23) DURING A LOCAL FLIGHT, AIRCRAFT SUFFERED ELECTRICAL MALFUNCTION WHICH RENDERED COMMUNICATION AND PANEL INDICATIONS INOPERATIVE, UPON SIGNAL FROM TOWER, A/C PROCEEDED TO LAND, AND ON TOUCHDOWN THE RIGHT MAIN AND NOSE GEAR COLLAPSED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX99LA219](https://openairdocs.org/ntsb/LAX99LA219), Jun 5, 1999: Beech A-36 (N126GL), Van Nuys, CA, substantial damage. Probable cause: The failure of the pilot to verify that the alternator was activated after engine start, subsequently resulting in a total electrical failure; and his inadequate emergency procedures for manual…

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.
