20130726019429A

Accident · Destroyed

FAA accident report · Enstrom F-28A · Danbury, TX · July 26, 2013

Date
July 26, 2013 · 13:15 local
Place
Danbury, TX
Airport
Salaika (Pvt)
Phase of flight
Takeoff: Climb Out
Operating rules
General operating rules (Part 91)
Operator
GWHS
Damage
Destroyed
Aircraft
N287Q
NTSB investigation
NTSBCEN13LA437
Reported as
Enstrom F-28A
Reported engine
Lycoming I0360 series
People aboard
2
Fatal injuries
0
Other injuries
2
Pilot’s certificates
Commercial pilot, flight instructor, private pilot
Pilot’s flight hours
2,000 total1,700 in this make and model80 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On July 26, 2013 the houston flight standards district office (FSDO) was notified of a helicopter crash in Danbury, Texas. The aircraft was reported as N287Q, an Enstrom F28A helicopter. The pilots were reported as privacy data omitted and privacy data omitted. Upon arrival at the accident scene the aircraft was positively identified as N287Q, by the houston FSDO. The wreckage was approximately 200 yards north of Salaika aviation?s hangar. The pilots had both been transported to the hospital with severe injuries. The aircraft was completely destroyed by fire, with most components melted. Due to the extensive and catastrophic damage it was determined to be an accident.

On July 29, 2013 a review of the aircraft records was conducted by the houston FSDO. No discrepancies were noted.

On August 1, 2013 the houston FSDO along with a representative from Enstrom helicopters, inspected the wreckage. There were no significant findings associated with the review. The Enstrom representative and the houston FSDO were unable to identify the failed component due to the extensive damage to the aircraft.

On August 7, 2013 the pilot in command was interviewed. He reported a control failure of the collective and the cyclic.

All airman and aircraft documentation was in order. The airman reported a mechanical failure resulting in the loss of aircraft control. The mechanical problem could not be identified directly due to extensive damage caused by the post crash fire.

As the FAA filed it

ON JULY 26, 2013 THE HOUSTON FLIGHT STANDARDS DISTRICT OFFICE (FSDO) WAS NOTIFIED OF A HELICOPTER CRASH IN DANBURY, TEXAS. THE AIRCRAFT WAS REPORTED AS N287Q, AN ENSTROM F28A HELICOPTER. THE PILOTS WERE REPORTED AS ^PRIVACY DATA OMITTED^ AND ^PRIVACY DATA OMITTED^. UPON ARRIVAL AT THE ACCIDENT SCENE THE AIRCRAFT WAS POSITIVELY IDENTIFIED AS N287Q, BY THE HOUSTON FSDO. THE WRECKAGE WAS APPROXIMATELY 200 YARDS NORTH OF SALAIKA AVIATION?S HANGAR. THE PILOTS HAD BOTH BEEN TRANSPORTED TO THE HOSPITAL WITH SEVERE INJURIES. THE AIRCRAFT WAS COMPLETELY DESTROYED BY FIRE, WITH MOST COMPONENTS MELTED. DUE TO THE EXTENSIVE AND CATASTROPHIC DAMAGE IT WAS DETERMINED TO BE AN ACCIDENT.

ON JULY 29, 2013 A REVIEW OF THE AIRCRAFT RECORDS WAS CONDUCTED BY THE HOUSTON FSDO. NO DISCREPANCIES WERE NOTED.

ON AUGUST 1, 2013 THE HOUSTON FSDO ALONG WITH A REPRESENTATIVE FROM ENSTROM HELICOPTERS, INSPECTED THE WRECKAGE. THERE WERE NO SIGNIFICANT FINDINGS ASSOCIATED WITH THE REVIEW. THE ENSTROM REPRESENTATIVE AND THE HOUSTON FSDO WERE UNABLE TO IDENTIFY THE FAILED COMPONENT DUE TO THE EXTENSIVE DAMAGE TO THE AIRCRAFT.

ON AUGUST 7, 2013 THE PILOT IN COMMAND WAS INTERVIEWED. HE REPORTED A CONTROL FAILURE OF THE COLLECTIVE AND THE CYCLIC.

ALL AIRMAN AND AIRCRAFT DOCUMENTATION WAS IN ORDER. THE AIRMAN REPORTED A MECHANICAL FAILURE RESULTING IN THE LOSS OF AIRCRAFT CONTROL. THE MECHANICAL PROBLEM COULD NOT BE IDENTIFIED DIRECTLY DUE TO EXTENSIVE DAMAGE CAUSED BY THE POST CRASH FIRE.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N287Q · 4

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