# Incident 20040229006089I: Gulstm 680F, San Diego, CA, February 29, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 29, 2004, 20:47 local time
- Place: San Diego, CA
- Airport: Montgomery Field Airport
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 32.7153° N, 117.1573° W: Placed by OpenAirDocs: center of San Diego, CA, within about 10 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.7153&lon=-117.1573&mi=10
- Aircraft: N680RR, registered now (https://openairdocs.org/aircraft/N680RR) (OpenAirDocs)
- Registry model: Aero Commander 680-F (registry code 0141606, https://openairdocs.org/model/aero-commander-680-f) (OpenAirDocs)
- Registry engine: Lycoming IGSO-540-B1A (registry code 41535, https://openairdocs.org/engine/lycoming-igso-540-b1a) (OpenAirDocs)
- Reported make and model: GULSTM 680F
- Reported engine: LYC IGSO540*
- People aboard: 4
- Fatal injuries: 0
- Pilot flight hours: 2,083 total, 450 in this make and model, 17 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040229006089I

## Narrative

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

(-23) PILOT WAS CONCLUDING AN IFR FLIGHT FROM HHR (HAWTHORNE) TO MYF (MONTGOMERY FIELD). FOLLOWING ILS APPROACH TO RUNWAY 28R, PILOT TOUCHED DOWN AND EMPLOYED HIS USUAL PROCEDURE OF HOLDING THE NOSE WHEEL OFF THE GROUND AS LONG AS POSSIBLE, TO FACILITATE DECELERATION AND MINIMIZE USE OF BRAKES. UPON LOWERING NOSE ON ROLLOUT, PILOT REALIZED HE WAS CLOSE TO END OF RUNWAY. MAXIMUM BRAKING FAILED TO STOP AIRCRAFT BEFORE END OF RUNWAY, RESULTING IN OVERRUN, WITH DAMAGE TO NOSE WHEEL AND TIRE. PILOT HAD NOTED LENGTH OF RUNWAY AS 4500 FT., BUT FAILED TO NOTE DISPLACED THRESHOLD, EFFECTIVELY LEAVING 2638 FEET USABLE LENGHT UTILIZING THE GLIDE SLOPE.

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.