# Accident 19801001045629A: Beech F33A, Arlington, AZ, October 1, 1980

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 1, 1980, 07:25 local time
- Place: Arlington, AZ
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: Pilot school (Part 141)
- Location: 33.3346° N, 112.7747° W: Placed by OpenAirDocs: center of Arlington, AZ, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.3346&lon=-112.7747&mi=10
- Aircraft: N6742D, a cancelled registration (https://openairdocs.org/deregistered/N6742D-1991-02-26) (OpenAirDocs)
- Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs)
- Reported make and model: BEECH F33A
- Fatal injuries: 0
- Pilot flight hours: 10,226 total, 2,455 in this make and model, 356 in the last 90 days
- NTSB investigation: [NTSB LAX81FUJ01](https://openairdocs.org/ntsb/LAX81FUJ01) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19801001045629A

## Narrative

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

PROPELLOR BLADE SEPARATED IN FLIGHT. CRASH-LANDED.

## 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 LAX81FUJ01](https://openairdocs.org/ntsb/LAX81FUJ01), Oct 1, 1980: Beech F33A (N6742D), Arlington, AZ, substantial damage

## Other reports on N6742D (1)

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

- [Incident 19901011045179I](https://openairdocs.org/incident/19901011045179I), Oct 11, 1990: Beech F33A (N6742D), Salina, UT, Substantial damage. Pilot exit aircraft after taxiing to fuel pump. Left engine running and bumped throttle. Aircract hit fence.

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.