# Accident 20011026030929A: Amtr THORPT18, Longmont, CO, October 26, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 26, 2001, 12:25 local time
- Place: Longmont, CO
- Airport: Vance Brand Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.1697° N, 105.1097° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.1697&lon=-105.1097&mi=10
- Aircraft: N2819L, registered now (https://openairdocs.org/aircraft/N2819L) (OpenAirDocs)
- Registry model: Irwin Wayne R THORP T-18 (registry code 89510JJ, https://openairdocs.org/model/irwin-wayne-r-thorp-t-18) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: AMTR THORPT18
- NTSB investigation: [NTSB DEN02LA005](https://openairdocs.org/ntsb/DEN02LA005) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011026030929A

## Narrative

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

(-23) AIRCRAFT WAS BEING TEST FLOWN. ENGINE STARTED TO RUN ROUGH, PILOT ADJUSTED MIXTURE CONTROL, ENGINE SEEMED TO RUN FINE, THEN IT QUIT RUNNING. PILOT WAS FORCED TO LAND SHORT OF RUNWAY IN A HORSE PASTURE. DAMAGE RESULTED BECAUSE PILOT APPLIED HARD BRAKING AND INTITIATED A SHARP TURN TO AVOID A FENCE.

## 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 DEN02LA005](https://openairdocs.org/ntsb/DEN02LA005), Oct 26, 2001: Irwin Thorp T-18 (N2819L), Longmont, CO, substantial damage. Probable cause: The loss of engine power for undetermined reasons, which resulted in a forced landing. A contributing factor was the lack of suitable terrain for the forced landing

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.