# Accident 19920809029899A: Blanca 1730A, Sedona, AZ, August 9, 1992

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 9, 1992, 13:15 local time
- Place: Sedona, AZ
- Airport: Sedona Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 34.9391° N, 111.9401° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.9391&lon=-111.9401&mi=10
- Aircraft: N6649V, a cancelled registration (https://openairdocs.org/deregistered/N6649V-2017-10-23) (OpenAirDocs)
- Registry model: Bellanca 17-30A (registry code 1220433, https://openairdocs.org/model/bellanca-17-30a) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BLANCA 1730A
- Reported engine: CONT IO520K
- People aboard: 4
- Fatal injuries: 0
- Pilot flight hours: 300 total, 170 in this make and model, 75 in the last 90 days
- NTSB investigation: [NTSB LAX92LA341](https://openairdocs.org/ntsb/LAX92LA341) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19920809029899A

## Narrative

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

RIGHT MAIN GEAR COLLAPSED ON LANDING ROLL CAUSING GROUND LOOP. UPPER TRUNNION ATTACH WELD FAILED.

## 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 LAX92LA341](https://openairdocs.org/ntsb/LAX92LA341), Aug 9, 1992: Bellanca 17-30A (N6649V), Sedona, AZ, substantial damage. Probable cause: THE FAILURE OF THE FIXED BASE OPERATOR TO PROPERLY CONDUCT AN ANNUAL INSPECTION AND INADEQUATE COMPLIANCE WITH THE AIRWORTHINESS DIRECTIVE. CONTRIBUTING TO THIS ACCIDENT WAS THE TOTAL FAILURE OF THE…

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.