20080318832399I

Incident · No damage

FAA incident report · AMD Falcon · San Diego, CA · March 18, 2008

Date
March 18, 2008 · 17:40 local
Place
San Diego, CA
Airport
San Diego International
Phase of flight
Takeoff Ground Roll
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N168DJ
Reported as
AMD Falcon
People aboard
1
Fatal injuries
0
Pilot’s flight hours
0 total0 in this make and model0 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.

(-23) During takeoff from lindburgh field, San Diego, a Falcon 20 experienced an aural fire warning (horn), activated prior to V1, requiring an aborted takeoff. No fire detection zone lights annunciated. A fire warning system test was performed with all annunciator lights ok. It was determined that the aural fire warning was false. The aircraft returned to home base (henderson, NV) with no other anomalies.

As the FAA filed it

(-23) DURING TAKEOFF FROM LINDBURGH FIELD, SAN DIEGO, A FALCON 20 EXPERIENCED AN AURAL FIRE WARNING (HORN), ACTIVATED PRIOR TO V1, REQUIRING AN ABORTED TAKEOFF. NO FIRE DETECTION ZONE LIGHTS ANNUNCIATED. A FIRE WARNING SYSTEM TEST WAS PERFORMED WITH ALL ANNUNCIATOR LIGHTS OK. IT WAS DETERMINED THAT THE AURAL FIRE WARNING WAS FALSE. THE AIRCRAFT RETURNED TO HOME BASE (HENDERSON, NV) WITH NO OTHER ANOMALIES.