# Incident 20151103020829I: Stephen Hacker Company LLC LIGHTNING, Eden Prairie, MN, November 3, 2015

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 3, 2015, 16:30 local time
- Place: Eden Prairie, MN
- Airport: Flying Cloud
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 44.8275° N, 93.4586° W: Placed by OpenAirDocs at FLYING CLOUD (FCM), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.8275&lon=-93.4586&mi=10
- Aircraft: N335CE, registered now (https://openairdocs.org/aircraft/N335CE) (OpenAirDocs)
- Registry model: Stephen Hacker LIGHTNING (registry code 05628PD, https://openairdocs.org/model/stephen-hacker-lightning) (OpenAirDocs)
- Registry engine: Jabiru 3300 (registry code 34802, https://openairdocs.org/engine/jabiru-3300) (OpenAirDocs)
- Reported make and model: STEPHEN HACKER COMPANY LLC LIGHTNING
- Reported engine: JABIRU 3300
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 373 total, 265 in this make and model, 9 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20151103020829I

## Narrative

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

WHILE LANDING ON RUNWAY 18 AT FCM, AIRCRAFT DEPARTED RUNWAY TO THE RIGHT NEAR TAXIWAY B AND IMPACTED TAXIWAY SIGN AND LIGHT.  WINDS WERE REPORTED TO BE 160 @ 13 GUSTING TO 20.

## Other reports on N335CE (1)

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

- [Incident 20100304028939I](https://openairdocs.org/incident/20100304028939I), Mar 4, 2010: Stephen Hac LIGHTNING (N335CE), Eden Praire, MN, Minor damage. [privacy data omitted] Was practicing (solo)touch and go landing in his expermental aircraft. [privacy data omitted] Is training for his private pilot…

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.