SEA06CA192 · Amorde Glasair II-S RG
Amorde Glasair II-S RG · Accident: loss of control on ground/water during landing
From Bozeman Yellowstone International Airport (BZN) to Rockford Municipal Airport (2U4)
Event
- NTSB case
- SEA06CA192
- 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
Amorde Glasair II-S RG
- Aircraft type
- Amorde GLASAIR II-S RG
- 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
- N183TA
- Operator
- Robert Goldman
- Onboard fatalities
- Unknown
- Route
- From Bozeman Yellowstone International Airport (BZN), Bozeman, MTTo Rockford Municipal Airport (2U4), Rockford, ID
- 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
- First occurrenceThe 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/water
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during cruise flight he noticed the aircraft's left wingtip fuel cap was missing. He stated fuel was not venting from the tip tank, however the airplane was accumulating ice and he was concerned that ice would collect over the open fuel port and potentially contaminate the fuel system. The pilot reported the aircraft continued to accumulate ice and eventually the airspeed indicator dropped to "zero" and the angle of attack indicator froze. The pilot declared an emergency and ultimately requested landing at the nearest airport, which was approximately 10 miles from his position. The pilot reported that as he "bleed airspeed off" for landing, approximately 5 feet above the runway, the airplane "pitched forward and dropped to the runway." The airplane bounced and eventually came to rest off the runway. The pilot reported the runway was 2,800 feet in length and the winds were from 180 degrees at 14 knots, gusting to 20 knots. The temperature at the airport was approximately 50 degrees F.
Probable cause
The pilot's failure to maintain aircraft control during landing. A contributing factor was gusty winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06CA192
- Event ID
- 20061114X01667
- Case number
- SEA06CA192
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: b6a95aab4cc2afdd3070721026e2b3b921fd76ac014082a203feae7f2cdeb525; retrieved 2026-09-22T04:25:53.414Z.