FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC94LA140 · Aces High CUBY B

24 Jul 1994 · Waterbury, CT, United States

Aces High CUBY B · Accident: total loss of engine power (non-mechanical) during initial climb

From Waterbury Airport (N41) to Waterbury Airport (N41)

Report a problem

Event

NTSB case
NYC94LA140
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

Aces High CUBY B

Aircraft type
Aces High CUBY
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
N2282Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Waterbury Airport (N41)To Waterbury Airport (N41)
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 (non-mechanical)
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
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Estimated position: the centre of Waterbury, CT, the place the record names. Not the accident site.

NTSB narrative

DURING THE INITIAL CLIMB AFTER TAKEOFF, THE ENGINE OF THE HOMEBUILT AIRPLANE EXPERIENCED A COMPLETE LOSS OF POWER. THE PILOT ATTEMPTED A 180 DEGREE TURN BACK TO THE AIRPORT, BUT THE AIRPLANE COLLIDED WITH TREES SHORT OF THE RUNWAY. EXAMINATION OF THE ENGINE REVEALED NO DISCREPANCIES. ACCORDING TO A CHART PUBLISHED BY THE FAA, THE TEMPERATURE AND DEW POINT WERE CONDUCIVE FOR MODERATE ICING DURING CRUISE POWER AND SERIOUS ICING DURING A POWERED GLIDE.

Probable cause

A LOSS OF ENGINE POWER FOR UNDETERMINED REASONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC94LA140
Event ID
20001206X01851
Case number
NYC94LA140
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: 527fe92eced66d64091673e05f2abd90de0e57446d9ee6c62323c0557d889384; retrieved 2026-09-21T13:45:39.106Z.