# Incident 20030703013119I: Amd FALCON50MYST, Carlsbad, CA, July 3, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 3, 2003, 19:30 local time
- Place: Carlsbad, CA
- Airport: Mcclellan-Palomar
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Operator: MHAA
- Location: 33.1283° N, 117.2801° W: Placed by OpenAirDocs at MC CLELLAN-PALOMAR (CRQ), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.1283&lon=-117.2801&mi=10
- Aircraft: N678MA, a cancelled registration (https://openairdocs.org/deregistered/N678MA-2019-02-12) (OpenAirDocs)
- Registry model: Dassault-Breguet FALCON 50 (registry code 2730106, https://openairdocs.org/model/dassault-breguet-falcon-50) (OpenAirDocs)
- Registry engine: AiResearch TFE731 series (registry code 01518, https://openairdocs.org/engine/airesearch-tfe731-series) (OpenAirDocs)
- Reported make and model: AMD FALCON50MYST
- Fatal injuries: 0
- Pilot flight hours: 26,200 total, 2,850 in this make and model, 164 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030703013119I

## Narrative

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

(-23) UNDER INVESTIGATION. (-23 AMENDMENT) THE AIRCRAFT LANDED FAST AND HARD, USING APPROXIMATELY ONE HALF OF RUNWAY 24. THE AIRCRAFT BLEW ONE TIRE ON EACH MAIN LANDING GEAR AND FAILED TO STOP BEFORE SKIDDING OFF OF THE RUNWAY CAUSING DAMAGE. ALSO SUSPECT AIRCRAFT MAY HAVE BEEN OVERWEIGHT. INVESTIGATION BY FSDO A/W INSPECTOR AND THE AIRFRAME MANUFACTURER COULD FIND NO DISCREPANCIES WITH THE AIRCRAFT BRAKING SYSTEM, ALTHOUGH THE COMPONENTS ARE BEING RETURNED TO THE MANUFACTURER FOR FURTHER INSPECTION.                                               (-23 2ND AMENDMENT) BASED ON RELIABLE EVIDENCE OBTAINED FROM THE COMPANY CHIEF PILOT AND PILOT-IN-COMMAND OF THE SUBJECT AIRCRAFT, IT WAS DETERMINED THAT THE APPROACH AND LANDING WERE WITHIN THE MANUFACTURERS LIMITS AND GOOD OPERATING PRACTICES. THE AIRCRAFT BLEW ONE TIRE ON EACH MAIN LANDING GEAR AND FAILED TO STOP BEFORE SKIDDING OFF OF THE RUNWAY CAUSING DAMAGE.

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.