# Accident 20050211002559A: Gulstm 680V, Fort Wayne, IN, February 11, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 11, 2005, 13:50 local time
- Place: Fort Wayne, IN
- Airport: Fort Wayne Municipal - Baer Field
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 40.9783° N, 85.1950° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.9783&lon=-85.1950&mi=10
- Aircraft: N688TM, a cancelled registration (https://openairdocs.org/deregistered/N688TM-2024-02-09) (OpenAirDocs)
- Registry model: Aero Commander 680V (registry code 0141714, https://openairdocs.org/model/aero-commander-680v) (OpenAirDocs)
- Registry engine: AiResearch TPE331 series (registry code 01514, https://openairdocs.org/engine/airesearch-tpe331-series) (OpenAirDocs)
- Reported make and model: GULSTM 680V
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 9,200 total, 500 in this make and model, 25 in the last 90 days
- NTSB investigation: [NTSB CHI05LA071](https://openairdocs.org/ntsb/CHI05LA071) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050211002559A

## Narrative

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

(-23) LEFT MAIN LANDING GEAR COLLAPSED DURING LANDING RESULTING IN SUBSTANTIAL DAMAGE TO AIRCRAFT.

## 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 CHI05LA071](https://openairdocs.org/ntsb/CHI05LA071), Feb 11, 2005: Twin Commander Acft. 680V (N688TM), Fort Wayne, IN, substantial damage. Probable cause: The malfunction of the landing gear extension assembly during approach for undetermined reasons.

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.