# Incident 20220702011649I: Cessna 172M, Stephensville, MT, July 2, 2022

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 2, 2022, 13:30 local time
- Place: Stephensville, MT
- Airport: Stevensville
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Location: 46.5251° N, 114.0528° W: Placed by OpenAirDocs at STEVENSVILLE (32S), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=46.5251&lon=-114.0528&mi=10
- Aircraft: N93JS, registered now (https://openairdocs.org/aircraft/N93JS) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 60 total, 58 in this make and model, 16 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20220702011649I

## Narrative

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

THE PIC OF ^PRIVACY DATA OMITTED^, IS A STUDENT PILOT.  ON 7/1/22 HE DID SEVERAL SATISFACTORY TAKE OFFS AND LANDINGS WITH HIS INSTRUCTOR, ^PRIVACY DATA OMITTED^. ON 7/2/22, AFTER DISCUSSING THE FLIGHT, CHECKING WEATHER WITH HIS INSTRUCTOR, AND DOING A PREFLIGHT, ^PRIVACY DATA OMITTED^ DEPARTED MSO AND DID A NORMAL LANDING AT SALMON ID (KSMN) WITH NO ISSUES. AFTER A NORMAL TAKEOFF HE DEPARTED FOR STEVENSVILLE, MT (32S). AFTER COMPLETING TWO GO-AROUNDS (HE CAME IN A LITTLE HIGH EACH TIME), THE PIC LANDED AT 32S. THERE WAS LITTLE WIND AND THE AIRCRAFT TOUCHED DOWN ON THE LEFT MAIN FOLLOWED SHORTLY BY THE RIGHT MAIN.

WHEN THE FRONT TIRE CAME DOWN RIGHT AFTER THE AIRCRAFT STARTED PULLING HARD TO THE RIGHT. THE PIC PUSHED ON THE LEFT RUDDER PETAL AND IT STILL PULLED RIGHT, SO HE STARTED PUSHING ON THE LEFT BRAKE TO NO AVAIL. THE AIRCRAFT WENT INTO THE GRASS AND THE PIC STARTED TO BRAKE WITH BOTH FEET. THE AIRCRAFT WENT THROUGH THE GRASS, HIT A DITCH, AND THEN ONTO A TAXI WAY. AFTER COMPLETING A SHUT DOWN ON THE TAXIWAY, THE PILOT DID A WALK AROUND AND SAW THAT THE FRONT TIRE WAS COMPLETELY FLAT.

THERE WAS NOT ENOUGH DAMAGE FOR THE NTSB TO GET INVOLVED. NEITHER THE PIC NOR THE MECHANIC WHO IS WORKING ON THE AIRCRAFT KNOW WHAT CAUSED THE TIRE TO GO FLAT.

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.