GAA17CA536 · Menzimer Gary RAY FIRESTAR II
Menzimer Gary RAY FIRESTAR II · Accident: loss of control in flight during landing
From Sharretts Airport (PN91) to Sharretts Airport (PN91)
Event
- NTSB case
- GAA17CA536
- 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
Menzimer Gary RAY FIRESTAR II
- Aircraft type
- Menzimer Gary Ray FIRESTAR
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sharretts Airport (PN91), Westfield, PATo Sharretts Airport (PN91), Westfield, PA
- Aircraft age
- About 20 years (built 1997)
- 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 in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the experimental amateur-built airplane reported in a written statement that he had recently purchased the accident airplane, and upon receiving it, he completed numerous taxi runs in a straight line but did not attempt to take off due to poor weather. He added that the airplane was hard to taxi in a straight line. He further reported that, days later, with improved weather, he decided to complete a "test flight."
He reported that, during the initial climb, the airplane "immediately started to drift to the left," and as the airplane continued to climb, the airplane "continued to make a left turn." He added that he applied right rudder and aileron and increased the power from 1/2 to 3/4 full but that the airplane continued to the left. He reported that he flew in the local area for about 20 minutes and could not resolve the left turning issue and that he was then concerned about the remaining fuel quantity, so he attempted to land at his private airstrip. He reported that he attempted two approaches, but the airplane continued turning to the left toward trees, and he performed go-arounds. During the third approach, he decided he would attempt to "touch down as quickly as possible," but during the landing flare, the airplane continued to the left and impacted trees.
The airplane was destroyed.
The pilot reported, "after replaying the accident in my mind, I decided that when I was doing my test taxiing, I might have been introvertly [sic] pressing the left trim button on the control stick. I might have done this several times which resulted in the crash."
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot did not submit the NTSB Form 6120.1 Pilot/ Operator Aircraft Accident/ Incident Report. He also did not report that he had received any recent flight training.
A Federal Aviation Administration aviation safety inspector reported that he located the electric rudder trim switch on top of the control stick and observed the rudder trim servo in the full-left-trim position. He further reported that the accident airplane was unregistered because the registration certificate had lapsed. He reported that the pilot, who was also the owner of the airplane, was required to renew the registration certificate. He added that the pilot reported to him that he had not flown as pilot-in-command for 20 years.
A technical representative for the experimental airplane kit manufacturer reported that the original kit design did not include electric trim for any flight control surfaces.
Probable cause
The pilot's improper decision to operate an airplane without recent flight training and his inadvertent application of left electric rudder trim before flight and a subsequent loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA536
- Event ID
- 20170914X15802
- Case number
- GAA17CA536
- 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: 8b10b82e8a40843415be5fee675d50ea3af45c524a1882a09e1e73007fc9348b; retrieved 2026-09-16T05:50:22.367Z.