# Accident 20020418006109A: Beech 76, Petaluma, CA, April 18, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 18, 2002, 19:20 local time
- Place: Petaluma, CA
- Airport: Petaluma Municipal Airport
- Damage: No damage
- Operating rules: Pilot school (Part 141)
- Operator: HZ8S
- Location: 38.2108° N, 122.7601° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.2108&lon=-122.7601&mi=10
- Aircraft: N6636J, a cancelled registration (https://openairdocs.org/deregistered/N6636J-2013-08-20) (OpenAirDocs)
- Registry model: Beech 76 (registry code 1153005, https://openairdocs.org/model/beech-76) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: BEECH 76
- NTSB investigation: [NTSB LAX02LA139](https://openairdocs.org/ntsb/LAX02LA139) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020418006109A

## Narrative

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

(-23) CFR COOPER STATED IN TELEPHONE INTERVIEW WITH MR. JEFF RICH OF THE NTSB, THE FOLLOWING POINTS: 1. HE ALLOWED THE STUDENT TO ENTER THE MANEUVER (ENGINE OUT GO-AROUND) AT TOO LOW AN ALTITUDE. 2. HE FAILED AS CFI TO EXERCISE COMMAND AUTHORITY AGGRESSIVELY ENOUGH TO AVOID THE CIRCUMSTANCES ENCOUNTERED. 3. UNDER THE CONDITIONS, THE WRONG ENGINE WAS SELECTED FOR INCREASED POWER.

## 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 LAX02LA139](https://openairdocs.org/ntsb/LAX02LA139), Apr 19, 2002: Beech 76 (N6636J), Petaluma, CA, substantial damage. Probable cause: The flight instructor's decision to execute a simulated single engine go-around at an altitude insufficient to preclude the inadvertent ground contact of the airplane and the resultant loss of…

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.