FTW95LA257 · Rocky Mountain BUCCANEER 11 B2B BUCCANEER
Rocky Mountain BUCCANEER 11 B2B BUCCANEER · Accident: total loss of engine power (mechanical failure) during initial climb
From 2V2 · CO to an unrecorded destination
Event
- NTSB case
- FTW95LA257
- 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
- 1 · 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
Rocky Mountain BUCCANEER 11 B2B BUCCANEER
- Aircraft type
- Rocky Mountain BUCCANEER 11 B2B
- 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
- N4093F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2V2 · COTo not recorded
- 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
- Initial climb
- 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
- Total loss of engine power (mechanical failure)
- 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
- Stall
- 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
- Pilot in command › Airspeed(vs), not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITNESSES SAID THE ENGINE LOST POWER SHORTLY AFTER LIFTOFF AT 100 TO 200 FEET ALTITUDE AND THE PILOT BANKED RIGHT IN AN APPARENT ATTEMPT TO MAKE A FORCED LANDING IN A GRASSY FIELD. ONE WITNESS SAID THE AIRPLANE STALLED AND SPUN BEFORE COLLIDING WITH TERRAIN. ANOTHER WITNESS OBSERVED PREVIOUS FLIGHTS AND SAID THE ENGINE WOULD LOSE POWER AFTER TAKEOFF BUT THE PILOT WOULD LAND ON THE REMAINING RUNWAY. ENGINE EXAMINATION DISCLOSED TIGHT METAL TIES BINDING THE FUEL LINE AGAINST THE STRUCTURE. THE VACUUM-OPERATED FUEL PUMP WAS MOUNTED ON FLEXIBLE PLASTIC STRIPS, ALLOWING IT TO VIBRATE. PERSONNEL WHO EXAMINED THE WRECKAGE REPORTED THAT THIS COULD CAUSE THE PUMP TO CAVITATE. THE PILOT HAD LOGGED 1.6 HOURS IN THE AIRPLANE 10 MONTHS BEFORE THE ACCIDENT.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN FLYING SPEED, RESULTING IN AN INADVERTENT STALL WHILE ATTEMPTING TO MAKE A FORCED LANDING. FACTORS WERE THE PILOT'S LACK OF TOTAL EXPERIENCE IN AIRPLANE MAKE/MODEL, IMPROPER MAINTENANCE OF THE AIRPLANE, AND OPERATION OF THE AIRPLANE WITH UNIDENTIFIED DEFICIENCIES IN EQUIPMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA257
- Event ID
- 20001207X03716
- Case number
- FTW95LA257
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-06-23.
- API snapshot SHA-256: a67e519a4187b589af1c69c4a42e4c2015dc855b3899d9e07cfb4aea7a9e0729; retrieved 2026-09-20T23:43:48.368Z.