BFO92LA112 · James Snyder CHALLENGER II CHALLENGER
James Snyder CHALLENGER II CHALLENGER · Accident: loss of engine power en route
From an unrecorded airport to 22B
Event
- NTSB case
- BFO92LA112
- 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
- 0
- 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
James Snyder CHALLENGER II CHALLENGER
- Aircraft type
- James Snyder CHALLENGER
- 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
- N602CH
- Operator
- James Snyder
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 22B
- 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
- En route · cruise
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Estimated position: the centre of Burlington, CT, the place the record names. Not the accident site.
NTSB narrative
THE STUDENT PILOT WAS ON A LOCAL FLIGHT FOR ABOUT 45 MINUTES, WHEN HE TRIED TO ACCELERATE, THE AIRPLANE DID NOT ATTAIN FULL POWER OF 6100 RPM. THE MAXIMUM WAS 4000 RPM FOLLOWED BY A FURTHER DROP TO 2200 RPM. HE TRIED TO REGAIN POWER BY APPLYING THE CHOKE, PRIMING THE ENGINE, SWITCHING MAGNETOS, AND TURNING OFF NON-ESSENTIAL POWER, BUT ALL WERE UNSUCCESSFUL. HE TRIED TO LAND ON A ROAD; HOWEVER DURING TOUCHDOWN HE OBSERVED TWO PERSONS APPROACHING HIM, ONE ON A BIKE, AND THE OTHER IN A CAR. HE TRIED TO AVOID HITTING THEM AND VEERED TO THE RIGHT SIDE OF THE ROAD, BUT HE COLLIDED WITH A STREET SIGN AND TELEPHONE POLE. EXAMINATION OF THE AIRPLANE BY THE FAA INCLUDED AN ENGINE RUN, AND INSPECTION OF THE FUEL SYSTEM. ACCORDING TO THE FAA THE ENGINE OPERATED AT 6100 RPM FOR A DURATION OF 5 MINUTES. THE LOSS OF POWER COULD NOT BE DUPLICATED. THERE WAS 6 GALLONS OF FUEL ON BOARD AND APPEARED TO HAVE OIL MIXED WITH GAS.
Probable cause
THE LOSS OF ENGINE POWER FOR UNDETERMINED REASONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92LA112
- Event ID
- 20001211X15079
- Case number
- BFO92LA112
- 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. 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: 25d18972ab07ba5051644f46e54c63fdbfe72a35569f7b3132ed70148614c401; retrieved 2026-09-23T02:55:17.793Z.