# Accident 19920722030079A: Amtrqc CHALLENGER2, Burlington, CT, July 22, 1992

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 22, 1992, 19:05 local time
- Place: Burlington, CT
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 41.7693° N, 72.9645° W: Placed by OpenAirDocs: center of Burlington, CT, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.7693&lon=-72.9645&mi=10
- Aircraft: N602CH, a cancelled registration (https://openairdocs.org/deregistered/N602CH-2013-09-30) (OpenAirDocs)
- Registry model: Snyder James C CHALLENGER II (registry code 05676QR, https://openairdocs.org/model/snyder-james-c-challenger-ii) (OpenAirDocs)
- Registry engine: Bombardier ROTAX (ALL) (registry code 09050, https://openairdocs.org/engine/bombardier-rotax-all) (OpenAirDocs)
- Reported make and model: AMTRQC CHALLENGER2
- Reported engine: ROTAX ROTAX503
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 100 total, 43 in this make and model
- NTSB investigation: [NTSB BFO92LA112](https://openairdocs.org/ntsb/BFO92LA112) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19920722030079A

## Narrative

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

REPORTED POWER LOSS. STRUCK TELEPHONE POLE AND SIGN LANDING ON ROAD. ENGINE TEST NORMAL POST ACCIDENT.

## 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 BFO92LA112](https://openairdocs.org/ntsb/BFO92LA112), Jul 22, 1992: James Snyder Challenger II (N602CH), Burlington, CT, substantial damage. Probable cause: THE LOSS OF ENGINE POWER 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.