# Accident 20010609015879A: Luscom 8E, Longmont, CO, June 9, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 9, 2001, 14:30 local time
- Place: Longmont, CO
- Airport: Vance Brand Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.1698° N, 105.2101° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.1698&lon=-105.2101&mi=10
- Aircraft: N1614K, a cancelled registration (https://openairdocs.org/deregistered/N1614K-2007-02-01) (OpenAirDocs)
- Registry model: Luscombe 8E (registry code 8190112, https://openairdocs.org/model/luscombe-8e) (OpenAirDocs)
- Registry engine: Lycoming 0-290 series (registry code 41506, https://openairdocs.org/engine/lycoming-0-290-series) (OpenAirDocs)
- Reported make and model: LUSCOM 8E
- Pilot certificates: Student
- NTSB investigation: [NTSB DEN01LA115](https://openairdocs.org/ntsb/DEN01LA115) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010609015879A

## Narrative

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

(-23) THE STUDENT PILOT SWERVED OFF THE RUNWAY DURING A LANDING AND RAN INTO A TAXIWAY THAT WAS UNDER CONSTRUCTION. THE AIRCRAFT'S RIGHT MAIN LANDING GEAR, FUSELAGE, AND PROPELLER WERE DAMAGED WHEN THE AIRCRAFT HIT THE NEW CEMENT TAXIWAY.  THE PILOT DID NOT KNOW WHY THE AIRCRAFT SWERVED OFF THE RUNWAY, BUT SUSPECTED A CROSSWIND CAUSED THE PROBLEM.

## 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 DEN01LA115](https://openairdocs.org/ntsb/DEN01LA115), Jun 9, 2001: Luscombe 8E (N1614K), Longmont, CO, substantial damage. Probable cause: the pilot's failure to maintain directional control during landing. A contributing factor was the tailwind.

## Other reports on N1614K (2)

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

- [Accident 20030816019809A](https://openairdocs.org/incident/20030816019809A), Aug 16, 2003: Luscom 8E (N1614K), Longmont, CO, Substantial damage. (-23) Aircraft was doing touch and go landings at (2V2). According to the pilot he noticed a slight left yaw on the last takeoff. The subsequent landing was…
- [Incident 19920505030159I](https://openairdocs.org/incident/19920505030159I), May 5, 1992: Luscom 8E (N1614K), Portland, OR. Partial engine power loss en route. Forced landing. Fuel selector handle over rotated. Partial fuel starvation.

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.