North American T28A accident near Ontario, Oregon, August 9, 2019
On August 9, 2019 at about 10:20 pm local time, a North American T28A, registered N9862C, was substantially damaged in an accident during approach (VFR pattern crosswind) near Ontario, Oregon (Ontario Muni airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power due to the improperly adjusted carburetor idle valve.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 9, 2019 · about 10:20 pm local time · cases in 2019
- Place
- Ontario, Oregon · Ontario Muni · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- North American T28A · all T28As on the register
- Registration
- N9862C · no longer on the register · serial 49-1727A
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot and one passenger were conducting a flight to test the landing gear. Following a low pass over the runway, the engine lost total power, and the pilot performed a forced landing to a field, during which he was fatally injured, and the passenger sustained serious injuries. Postaccident examination of the carburetor revealed that, when the throttle arm was placed near the idle position, the internal idle valve was closed, which restricted fuel from flowing through the carburetor at lower power settings and likely resulted in the loss of engine power. It is likely that the pilot reduced the engine power during the low pass to a setting that would have allowed for the idle valve to close completely, thereby restricting the fuel flow. No additional anomalies were noted with the engine or airframe. The airplane had not flown for about 8 years and had undergone maintenance for the previous 10 months before it first flew 6 days before the accident. One of the maintenance items performed included installation of a new carburetor. The mechanic who performed the annual inspection reported that he assisted in adjusting the idle setting on the carburetor. Whether any additional maintenance was performed on the carburetor before the accident flight could not be determined, and the engine logbook was not available for review.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during approach (VFR pattern crosswind) defining event
- Off-field or emergency landing during approach (VFR pattern crosswind)
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel control/carburetor › Incorrect service/maintenance other cases naming the engine
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 4,668 hours in all
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: frt
- Injury: fatal
The aircraft
- Airframe total time: 2,378 hours
- Last inspection: annual inspection, August 4, 2019; 1 hours since
- Maximum gross weight: 8,501 lb
- Seats: 2
- Landing gear: retractable
- Engine: Kaiser R1300-1B (piston); 0 hours total
The flight
- Departed from: ONO Ontario OR at 10:00 pm
- Destination: ONO Ontario OR
- Flight plan: none
- Runway 33, 5,006 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 170° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 52°F (11°C)
- Altimeter: 29.84 inHg
- Observation at 9:53 pm from KONO, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Photographs from the investigation 5 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – View of the accident site and main wreckage.
Photo 2 - View of the accident site and main wreckage.
Photo 3 - View of the accident site and main wreckage.
Photo 4 - View of the recovered wreckage.
Photo 5 - View of the propeller.The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
16 documents, released by the NTSB on February 8, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
Connections how this case links to the rest of the register
- N9862C: not on the register today · the record of its deregistration
- North American T-28 206 registered today · the model family and its accident history
- North American 1,297 aircraft on the register
- Engine: Kaiser R1300-1B · as the NTSB recorded it
- Ontario Municipal · nearest airport
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,008 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR19FA215.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.