# Incident 19980920032729I: Beech E33A, Monterey, CA, September 20, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 20, 1998, 13:48 local time
- Place: Monterey, CA
- Airport: Monterey Peninsula
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 36.6012° N, 121.8828° W: Placed by OpenAirDocs: center of Monterey, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.6012&lon=-121.8828&mi=10
- Aircraft: N8377N, registered now (https://openairdocs.org/aircraft/N8377N) (OpenAirDocs)
- Registry model: Beech E33A (registry code 1151424, https://openairdocs.org/model/beech-e33a) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH E33A
- Reported engine: CONT IO520*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 20,000 total, 3,200 in this make and model, 150 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980920032729I

## Narrative

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

NO FLAPS ON WEST LANDING 28L MONTEREY. GREEN LIGHT ON SINGLE LIGHT FOR GEAR DOWN. PILOT STATED "I DID NOT ELEVATE NOSE GEAR WINDOW FOR GEAR DOWN POSITION, ON ROLL OUT NOSE GEAR COLLAPSED." AIRCRAFT HAS BEEN FERRIED TO CHOWCHILLA CA FOR REPAIR, ALL EQUIREMENTS SPECIFIED IN THE SPECIAL FERRY PERMIT HAVE BEEN ACCOMPLISHED.

## Other reports on N8377N (1)

Matched to the same aircraft by N-number and date.

- [Incident 20030703022929I](https://openairdocs.org/incident/20030703022929I), Jul 3, 2003: Beech E33A (N8377N), Reno, NV, Minor damage. (-23) Pilot taxied aircraft in early morning light and failed to follow a path to avoid collision with concrete curb. Aircraft nose wheel collapsed and prop…

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.