# Accident 20130805014579A: Embraer S A EMB-505, Eden Prairie, MN, August 5, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 5, 2013, 08:48 local time
- Place: Eden Prairie, MN
- Airport: Flying Cloud
- Damage: Substantial damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Operator: DJFA
- Location: 44.8267° N, 93.4475° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.8267&lon=-93.4475&mi=10
- Aircraft: N327FL (not matched to a registry record)
- Reported make and model: EMBRAER S A EMB-505
- Reported engine: P&W CANADA PW535E
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 7,500 total, 1,600 in this make and model, 100 in the last 90 days
- NTSB investigation: [NTSB CEN13LA462](https://openairdocs.org/ntsb/CEN13LA462) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130805014579A

## Narrative

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

AIRCRAFT WAS ON A REPOSITIONING FLIGHT TO FCM WITH 2 PILOTS ON BOARD AND NO PASSENGERS.  AIRCRAFT LANDED ON RUNWAY 10R AT FCM AND DEPARTED END OF RUNWAY.  THE PIC AND SIC BOTH STATED WHEN THEY REALIZED THEY WERE GOING TO GO OFF THE END OF THE RUNWAY, THEY ATTEPMTED TO STEER TO THE LEFT TO ATTEMPT TO STOP IN THE OPEN AREA AND AVOID THE PERIMETER FENCE AND HIGHWAY.  THE AIRCRAFT WENT THROUGH THE PERIMETER FENCE AND STOPPED JUST SHORT OF THE HIGHWAY.

## 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 CEN13LA462](https://openairdocs.org/ntsb/CEN13LA462), Aug 5, 2013: Embraer S A EMB-505 (N327FL), Eden Prairie, MN, substantial damage. Probable cause: The flight crew's failure to execute a go-around during a non-stabilized approach, which resulted in a runway overrun.

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.