CEN19LA241 · Stoddard-Hamilton GlaStar
Stoddard-Hamilton GlaStar · Accident: loss of control on ground during landing
From Rochester International Airport (RST) to Rochester International Airport (RST)
Event
- NTSB case
- CEN19LA241
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Stoddard-Hamilton GlaStar
- Aircraft type
- Stoddard Hamilton GLASTAR
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N98PW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rochester International Airport (RST), Rochester, MNTo Rochester International Airport (RST), Rochester, MN
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he departed on a multileg cross-country flight with several planned refueling stops. He had no difficulty landing at the first stop. During the landing at the second stop, the airplane veered hard to the right. The pilot applied left rudder but was unable to turn the airplane back toward the runway. He applied full throttle in an attempt to go around. The airplane continued through the grass and struck a berm, which resulted in substantial damage to the airplane. A mechanic later examined the airplane and reported that the brake functioned normally and that the right tire showed no evidence of a flat spot or skid marks on the tire tread. The pilot said he did not believe the right wheel had "locked up" but rather that the right brake had become stuck and would not release. Investigators were not able to determine why the airplane veered on landing.
Probable cause
A loss of directional control on landing for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA241
- Event ID
- 20190728X21500
- Case number
- CEN19LA241
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 7286595d718362cefb31e2df371b152ba0278525473978f4fcbd6503075bbddb; retrieved 2026-09-16T09:35:17.527Z.