No fatalities

Piper PA-28-161 F-GGFX Collision with Fence at Chavenay-Villepreux

FR

On April 10, 2013, a Piper PA 28-161 (registration F-GGFX) was involved in an aviation accident near FR. No fatalities were reported. Investigators recorded the probable cause as: The lack of a common action plan between the instructor and pilot after the simulated engine failure, combined with a long flare and the pilot's surprise at the go-around request, resulted in insufficient takeoff distance to avoid a non-frangible obstacle in… This summary draws on records from the French Bureau d'Enquêtes et d'Analyses (BEA); 4 related events involving the same aircraft type or operator are linked below.

Sourcesthe French Bureau d'Enquêtes et d'Analyses (BEA)Primary reportUpdated 2026-10-18Data APIEditorial standards

On 10 April 2013, a Piper PA-28-161 (F-GGFX) struck a fence after a go-around during an instructional flight at Chavenay-Villepreux, resulting in heavy damage.

Incident Overview and Flight Details On 10 April 2013 at 18:40 local time, a Piper PA-28-161 registered F-GGFX, operated by a club, was conducting a local instructional flight at Chavenay-Villepreux aerodrome (78). The aircraft was carrying a pilot and an instructor. During the flight, the pilot performed a simulated engine failure exercise and landed on runway 23. While rolling out, the pilot initiated a go-around. The aircraft subsequently struck the lower part of the aerodrome perimeter fence located immediately beyond the runway end and came to rest 90 meters past the fence. The aircraft sustained heavy damage. ## Operational Context and Testimonies The instructor stated that the plan was to conduct a simulated engine failure followed by a traffic pattern. During the landing rollout, the instructor requested the pilot to perform a new traffic pattern. After applying power, the instructor saw the fence and believed it could be avoided. The pilot reported that the landing flare was long and that they expected a full stop. The pilot was surprised by the instructor's request to perform a touch-and-go for another traffic pattern. The air traffic controller noted that the pilot was given the option to either land or perform a touch-and-go. The controller observed the aircraft decelerating significantly during the rollout, suggesting a full stop, and heard the engine power up after the aircraft had passed the runway intersection. ## Aerodrome Information and Regulatory Background In August 2012, an audit by the DSAC identified that the non-frangible perimeter fence penetrated the departure path for QFU 23. The audit concluded that fence locations needed to be considered in declared distances to better protect departure paths. In response, the aerodrome manager proposed immediate measures to indicate the fence's presence and height in aeronautical information, followed by a permanent instruction to 'maintain runway centerline on takeoff' for QFU 05 and 23. In March 2013, the DSAC Nord issued the aerodrome certification with specific conditions: publishing 'maintain runway centerline on takeoff' for QFU 05 and 23, and listing the fence height (1.20 m) in aeronautical information. A NOTAM modifying declared distances for runway 10-28 was published on 11 April 2013. The specific conditions were published by NOTAM on 4 September 2013, but this information was not present in the aeronautical documentation in effect on the day of the accident. ## Environmental and Aircraft Factors ATIS information reported a wind of 170 degrees at 8 knots, with runways described as 'wet and slippery' and 'degraded' on runway 05-23 due to recent rainfall making the ground soft. The aircraft was equipped with a Thielert TAE 125-01 engine of 135 hp. Performance calculations based on the flight manual, under estimated conditions (ISA, aerodrome altitude 424 ft, landing mass 985 kg, headwind 4 kt, LDA runway 23 727 m), were compatible with landing and takeoff distances. The pilot had approximately 500 flight hours and had not flown for three months. The instructor had over 26,000 hours on aircraft and about 300 hours on the PA-28, including 6 hours in the previous three months and 4 hours 30 minutes in the last 24 hours.

Probable cause

The lack of a common action plan between the instructor and pilot after the simulated engine failure, combined with a long flare and the pilot's surprise at the go-around request, resulted in insufficient takeoff distance to avoid a non-frangible obstacle in the departure path. The runway condition likely further degraded aircraft performance.

All Piper PA-28 Cherokee accidents →

Frequently asked questions

What happened in the 10 Apr 2013 Piper PA 28-161 accident near FR?

On 10 April 2013, a Piper PA-28-161 (F-GGFX) struck a fence after a go-around during an instructional flight at Chavenay-Villepreux, resulting in heavy damage.

Were there any fatalities in the 10 Apr 2013 Piper PA 28-161 accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 10 Apr 2013 involved a Piper PA 28-161, registration F-GGFX, at FR.

What was the probable cause of the accident?

The lack of a common action plan between the instructor and pilot after the simulated engine failure, combined with a long flare and the pilot's surprise at the go-around request, resulted in insufficient takeoff distance to avoid a non-frangible obstacle in the departure path. The runway condition likely further…