# Incident 20030223003429I: Cessna 172H, Longview, TX, February 23, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 23, 2003, 12:30 local time
- Place: Longview, TX
- Airport: Gregg County
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 32.5007° N, 94.7405° W: Placed by OpenAirDocs: center of Longview, TX, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.5007&lon=-94.7405&mi=10
- Aircraft: N1676F, registered now (https://openairdocs.org/aircraft/N1676F) (OpenAirDocs)
- Registry model: Cessna 172H (registry code 2072424, https://openairdocs.org/model/cessna-172h) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172H
- Pilot certificates: Student
- Pilot flight hours: 33 total, 33 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030223003429I

## Narrative

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

(-23) MR. JEFF BOLDING WAS ON A SOLO CROSS COUNTRY FROM LONGVIEW TO ABILENE, HE WAS MAKING POOR GROUND SPEED AND ALREADY BURNED 40 PERCENT OF HIS FUEL WHEN HE DECIDED TO TURN BACK TO LONGVIEW. MR. BOLDING WAS ALSO EXPERIENCING MODERATE TURBULENCE AT HIS ALTITUDE. UPON ARRIVAL AT LONGVIEW MR. BOLDING MADE AN ATTEMPT TO LAND ON RUNWAY 17 AS HE WAS INSTRUCTED FROM THE TOWER, THE WINDS WERE SO STRONG MR. BOLDING EXECUTED A GO-AROUND PROCEDURE AND CIRCLED THE FIELD TO TRY AGAIN. MR. BOLDING LANDED ON THE SECOND ATTEMPT AND HAD ALL THREE WHEELS ON THE GROUND WHEN A GUST OF WIND BLEW UP UNDER HIS WING AND THE AIRCRAFT GROUND LOOPED STRIKING THE PROP ON THE GROUND NUMEROUS TIMES. MR. BOLDING WAS NOT INJURED AND THE AIRCRAFT SUFFERED MINOR DAMAGE.

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.