OpenAirDocs.org

20040512008569I

Incident · Minor damage
Open the Markdown

FAA incident report · AMD FALCON 10 · Mesa, AZ · May 12, 2004

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
May 12, 2004 · 20:47 local
Place
Mesa, AZ
Airport
Falcon Field Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N5CA
Reported as
AMD FALCON10
Reported engine
Garrett TFE731*
People aboard
4
Fatal injuries
0
Pilot’s flight hours
15,000 total4,500 in this make and model25 in the last 90 days
N5CARegistered now · Dassault-Breguet FALCON 10S/N 187 · Built 1981Airframe modelDassault-Breguet FALCON 10Engine modelGarrett TFE731 seriesTurbo-fan

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.

(-23) Pilot statement (attached) indicates the flying pilot, Mr. Saiz, executed a normal landing approach for runway 22L (ffz). The pilot stated that the aircraft approach speed was normal and correct VASI indications were displayed. The pilot stated that the aircraft touched down in the first 3rd of the runway and the speed brakes were deployed and the thrust reversers were armed. When reverse thrust was applied the aircraft yawed to the left after which maximum (differential) braking was applied to stop the aircraft and maintain runway alignment. During the rollout the aircraft skidded off the runway into the overrun. The pax crew exited the aircraft and the aircraft was towed to a maintenance facility for inspection and repairs. Three of the tires were flat spotted and one tire was blown. Four tires were replaced and the wheels and hardware were sent out for inspection. Later inspection of the thrust reverser system determined that the failure of the thrust reverser was due to a faulty limit (micro) switch. The pilot was very cooperative and sent all supporting information to aid in the investigation.

As the FAA filed it

(-23) PILOT STATEMENT (ATTACHED) INDICATES THE FLYING PILOT, MR. SAIZ, EXECUTED A NORMAL LANDING APPROACH FOR RUNWAY 22L (FFZ). THE PILOT STATED THAT THE AIRCRAFT APPROACH SPEED WAS NORMAL AND CORRECT VASI INDICATIONS WERE DISPLAYED. THE PILOT STATED THAT THE AIRCRAFT TOUCHED DOWN IN THE FIRST 3RD OF THE RUNWAY AND THE SPEED BRAKES WERE DEPLOYED AND THE THRUST REVERSERS WERE ARMED. WHEN REVERSE THRUST WAS APPLIED THE AIRCRAFT YAWED TO THE LEFT AFTER WHICH MAXIMUM (DIFFERENTIAL) BRAKING WAS APPLIED TO STOP THE AIRCRAFT AND MAINTAIN RUNWAY ALIGNMENT. DURING THE ROLLOUT THE AIRCRAFT SKIDDED OFF THE RUNWAY INTO THE OVERRUN. THE PAX CREW EXITED THE AIRCRAFT AND THE AIRCRAFT WAS TOWED TO A MAINTENANCE FACILITY FOR INSPECTION AND REPAIRS. THREE OF THE TIRES WERE FLAT SPOTTED AND ONE TIRE WAS BLOWN. FOUR TIRES WERE REPLACED AND THE WHEELS AND HARDWARE WERE SENT OUT FOR INSPECTION. LATER INSPECTION OF THE THRUST REVERSER SYSTEM DETERMINED THAT THE FAILURE OF THE THRUST REVERSER WAS DUE TO A FAULTY LIMIT (MICRO) SWITCH. THE PILOT WAS VERY COOPERATIVE AND SENT ALL SUPPORTING INFORMATION TO AID IN THE INVESTIGATION.