SEA04LA046 · Jerome Q-2
Jerome Q-2 · Accident: loss of engine power on approach
From Portland Hillsboro Airport (HIO) to Portland Hillsboro Airport (HIO)
Event
- NTSB case
- SEA04LA046
- 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
Jerome Q-2
- Aircraft type
- Jerome Q-2
- 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
- N143GJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland Hillsboro Airport (HIO), Hillsboro, ORTo Portland Hillsboro Airport (HIO)
- 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
- Approach · VFR pattern downwind
- 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 engine power
- 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 › Proper descent rate, not maintained
- Pilot in command › Weather evaluation, inadequate
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 the Revmaster 2100DQ engine, a Volkswagen automobile engine modified for aircraft use, had just undergone maintenance work for a sticking valve and this was the first flight for the homebuilt aircraft following that maintenance. He took off in light drizzle, flew one circuit in the pattern and was climbing out for a second approach when he encountered heavy rain. The aircraft's engine began to run rough and the pilot applied carburetor heat but the partial power loss continued. He then received clearance to land and executed a rapid descent to a hard landing coming to rest near the midpoint of the 4,049 foot long asphalt runway. The temperature/dew point at the time of the accident at the site was 8/6 degrees Celsius respectively, and serious carburetor icing conditions existed.
Probable cause
The pilot's inadequate evaluation of deteriorating weather conditions (increasing rain) and his failure to maintain the proper rate of descent on landing (long/hard touchdown). Contributing factors were carburetor icing conditions and rain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04LA046
- Event ID
- 20040305X00272
- Case number
- SEA04LA046
- 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: 4b628bca7240326fe6edb97f6d90c843d9574dc2f789332727be30b954e10e70; retrieved 2026-09-21T19:17:20.569Z.