# Accident 20100811041329A: Aero Comman 500-B, Burns, OR, August 11, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 11, 2010, 08:55 local time
- Place: Burns, OR
- Airport: Burns Municipal
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 42.6586° N, 118.7447° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.6586&lon=-118.7447&mi=10
- Aircraft: N500FV, a cancelled registration (https://openairdocs.org/deregistered/N500FV-2017-05-16) (OpenAirDocs)
- Registry model: Aero Commander 500-B (registry code 0141106, https://openairdocs.org/model/aero-commander-500-b) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: AERO COMMAN 500-B
- Reported engine: CONT MOTOR I0-470 SERIES
- People aboard: 2
- Fatal injuries: 2
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,350 total, 0 in this make and model, 0 in the last 90 days
- NTSB investigation: [NTSB WPR10FA397](https://openairdocs.org/ntsb/WPR10FA397) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100811041329A

## Narrative

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

ON AUGUST 11, 2010, ABOUT 0855 PACIFIC DAYLIGHT TIME, AN AERO COMMANDER 500B, N500FV, IMPACTED THE TERRAIN ABOUT 87 MILES SOUTH OF BURNS, OREGEN. THE PRIVATE PILOT AND HIS PASSENGER WERE KILLED, AND THE AIRPLANE SUSTAINED SUBSTANRIAL DAMAGE. THE 14 CODE OF FEDERAL REGULATIONS PART 91 VISUAL FLIGHT RULES (VFR) FLIGHT, WHICH DEPARTED REDDING MUNICIPAL AIRPORT, REDDING, CALIFORNIA, AT AN AS OF YET UNDETERMINED TIME, WAS EN ROUTE TO POCATELLO, IDAHO. THE ACCIDENT TOOK PLACE IN A AREA WHERE THUNDERSTORMS, LIGHTNING AND RAIN WERE REPORTED. NO FLIGHT PLAN HAD BEEN FILED, BUT THE PILOT WAS RECEIVING RADAR FLIGHT FOLLOWING FROM AIR ROUTE TRAFFIC CONTROL.ACCORDING TO WITNESSESS IN THE AREA, THE AIRPLANE COULD BE HEARD OVERHEARD, BUT COULD NOT BE SEEN BECAUSE OF THE SOLID OVERCAST AND THE RAIN THAT WAS FALLING. THE WITNESSESS REPORTEDTHAT THE AIRPLANE SOUNDED NORMAL AT FIRST, BUT THEN SOUNDS COMING FROM THE ENGINES BECAME SIMILAR TO THOSE THAT THEY HAD HEARD FROM AN "AIRPLANE DOING AEROBATICS."  SOMR THEREAFTER, THE AIRPLANE WAS SEEN DESCENDING STEEPLY OUT OF THE CLOUDS WITH ABOUT ONE-THIRD OF THE LEFT WING MISSING.THE AIRPLANE IMPACTED THE TERRAIN IN A NEAR VERTICAL ATTITUDE.

## 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 WPR10FA397](https://openairdocs.org/ntsb/WPR10FA397), Aug 11, 2010: Aero Commander 500-B (N500FV), Burns, OR, substantial damage, 2 fatal. Probable cause: The non-instrument rated pilot's improper decision to continue flight into an area of known instrument meteorological conditions and his failure to maintain control of the airplane after entering…

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.