# Accident 19920620021222A: Amtr GLASAIR, Brighton, CO, June 20, 1992

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 20, 1992, 14:05 local time
- Place: Brighton, CO
- Airport: Brighton Van Aire Estates Airport
- Damage: Destroyed
- Collision: Midair collision, second aircraft
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: General operating rules (Part 91)
- Location: 39.9502° N, 104.7902° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.9502&lon=-104.7902&mi=10
- Aircraft: N32KW, a cancelled registration (https://openairdocs.org/deregistered/N32KW-1994-11-22) (OpenAirDocs)
- Registry model: Wells Kenneth N GLASAIR-SH2 (registry code 05655YL, https://openairdocs.org/model/wells-kenneth-n-glasair-sh2) (OpenAirDocs)
- Reported make and model: AMTR GLASAIR
- Reported engine: LYC O320B1B
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,454 total, 31 in the last 90 days
- NTSB investigation: [NTSB DEN92LA063](https://openairdocs.org/ntsb/DEN92LA063) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19920620021222A

## Narrative

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

BACK TAXIING ON RUNWAY WAS STRUCK BY DEPARTING N81229 THAT FAILED TO SEE HIM ON RUNWAY OR ASCERTAIN RUNWAY CLEAR.

## Other aircraft in the event

- N81229, Frchld 24W46: [Accident 19920620021221A](https://openairdocs.org/incident/19920620021221A)

## 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 DEN92LA063](https://openairdocs.org/ntsb/DEN92LA063), Jun 20, 1992: Wells GLASAIR-SH2 (N32KW), Brighton, CO, destroyed. Probable cause: THE PILOT'S INADEQUATE VISUAL LOOKOUT.

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.