# Incident 20160903016079I: Vans RV-7, Bluff, UT, September 3, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 3, 2016, 17:00 local time
- Place: Bluff, UT
- Airport: Bluff Airport
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 37.2550° N, 109.6330° W: Placed by OpenAirDocs at BLUFF (66V), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.2550&lon=-109.6330&mi=10
- Aircraft: N112AD, registered now (https://openairdocs.org/aircraft/N112AD) (OpenAirDocs)
- Registry model: Wltt RV-7 (registry code 05634AY, https://openairdocs.org/model/wltt-rv-7) (OpenAirDocs)
- Registry engine: Lycoming IO-390 series (registry code 41678, https://openairdocs.org/engine/lycoming-io-390-series) (OpenAirDocs)
- Reported make and model: VANS RV-7
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 520 total, 85 in this make and model, 22 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160903016079I

## Narrative

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

UPON TOUCHDOWN THE AIRCRAFT LEFT WINGTIP ROSE AND THE PILOT RESPONDED WITH SOME RUDDER INPUT AND A SMALL THROTTLE ADJUSTMENT TO COMPENSATE.  AS HE WAS DOING SO THE TAILWHEEL AIRPLANE TURNED HARD TO THE LEFT AND DEPARTED THE RUNWAY TO THE SIDE OF THE RUNWAY AND THE PILOT MADE THE DECISION TO APPLY FULL POWER TO INITIATE A GO-AROUND. HE WAS UNABLE TO GET THE AIRCRAFT BACK INTO THE AIR AND WHILE TRAVELLING THROUGH THE SANDY SURFACE, UNABLE TO AVOID A FENCE AND MADE CONTACT WITH 2 POSTS IN THE FENCE WHEN PASSING THROUGH AND CROSSED A SERVICE ROAD ON THE OTHER SIDE OF THE FENCE WHERE HE WAS ABLE TO GET THE AIRCRAFT STOPPED, SHUT DOWN AND EVACUTE HIMSELF AND HIS PASSENGER

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.