# Accident 20010828026469A: Amd FALCON, Detroit, MI, August 28, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 28, 2001, 17:11 local time
- Place: Detroit, MI
- Airport: Detroit City
- Damage: No damage
- Operating rules: Air taxi and commuter (Part 135)
- Operator: CXPA
- Location: 42.3995° N, 83.0002° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=42.3995&lon=-83.0002&mi=10
- Aircraft: N617GA, a cancelled registration (https://openairdocs.org/deregistered/N617GA-2007-02-27) (OpenAirDocs)
- Registry model: Dassault/Sud FAN JET FALCON (registry code 2720302, https://openairdocs.org/model/dassault-sud-fan-jet-falcon) (OpenAirDocs)
- Registry engine: GE CF700 series (registry code 30010, https://openairdocs.org/engine/ge-cf700-series) (OpenAirDocs)
- Reported make and model: AMD FALCON
- NTSB investigation: [NTSB CHI01LA296](https://openairdocs.org/ntsb/CHI01LA296) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010828026469A

## Narrative

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

(-23) AIRCRAFT TOOK OFF FROM DETROIT CITY ON RUNWAY 23 AT ABOUT 500 FEET AND INTO THE TURN @ 2204Z, PILOT REPORTED MAIN CARGO DOOR HAD COME OPEN. PILOT TURNED AIRCRAFT AROUND AND STARTED HIS APPROACH BACK TO CITY AIRPORT ON RUNWAY 33. AIRCRAFT CAME IN FAST, AND LONG, THUS NOT ALLOWING TIME FOR HTE MAIN GEAR EXTEND AND LOCK. AIRCRAFT LANDED ON THE RIM OF THE MAIN GEAR. PILOT CUT POWER, SKIDDED TO RIGHT OF RUNWAY 33 THROUGH THE FENCE AND CAME TO REST IN THE GRAVE YARD. THE COPILOT RECEIVED VERY MINOR INJURIES. AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE. (.19) ON AUGUST 28, 2001, ABOUT 1809 EASTERN DAYLIGHT TIME, A DASSAULT/SUD FAN JET FALCON, N617GA, PILOTED BY AN AIRLINE TRANSPORT PILOT RATED PILOT AND COMMERCIAL RATED CO-PILOT, SUSTAINED SUBSTANTIAL DAMAGE ON IMPACT WITH TERRAIN DURING A WHEELS UP LANDING ON RUNWAY 33 (5,090 FEET BY 100 FEET, DRY, GROOVED ASPHALT) AT DETROIT CITY AIRPORT (DET), DETROIT, MICHIGAN. THE AIRPLANE CAME TO REST OFF THE DEPARTURE END OF RUNWAY 33. THE NON-SCHEDULED DOMESTIC CARGO FLIGHT WAS OPERATING UNDER 14 CFR PART 135. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE FLIGHT WAS ON AN                                               IFR FLIGHT PLAN. THE PILOT AND CO-PILOT REPORTED NO INJURIES. THE FLIGHT ORIGINATED FROM DET AND WAS DESTINED FOR GREATER ROCKFORD AIRPORT, NEAR ROCKFORD, ILLINOIS. THE FLIGHT RETURNED TO DET FOR A LANDING AT THE TIME OF THE ACCIDENT.

## 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 CHI01LA296](https://openairdocs.org/ntsb/CHI01LA296), Aug 28, 2001: Dassault/SUD Fan Jet Falcon (N617GA), Detroit, MI, substantial damage. Probable cause: The wheels up landing performed by the flightcrew during the emergency landing and improper aircraft preflight by the pilot in command. Factors were the unsecured cargo door, the cemetery fence, and…

## Other reports on N617GA (2)

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

- [Incident 20000307022989I](https://openairdocs.org/incident/20000307022989I), Mar 7, 2000: Amd FALCON (N617GA), Louisville, KY. (-23)Pilot discrepancy report on gxpa flight log #458: "elevator travel on yoke from neutral to all the way back to the stops is 1/2 the distance ot other…
- [Accident 19980512008969A](https://openairdocs.org/incident/19980512008969A), May 12, 1998: Amd FALCON (N617GA), Monroe, MI, Substantial damage. Narrative: at vr pilot attempted to rotate and found the elevator locked. Pilot ran off end of runway. (.4)the pilot-in-command reported that the flight…

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.
