NYC02LA019 · Norton/Cloeren Titan Tornado II
Norton/Cloeren Titan Tornado II · Accident: loss of engine power
From Clearview Airpark (2W2) to Clearview Airpark (2W2)
Event
- NTSB case
- NYC02LA019
- 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
- 2 · 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
Norton/Cloeren Titan Tornado II
- Aircraft type
- Norton/cloeren TITAN TORNADO
- 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
- N996T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clearview Airpark (2W2), Westminster, MDTo Clearview Airpark (2W2), Westminster, MD
- 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
- Unknown
- 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
- 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
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane departed on a local VFR flight, and while flying in a rural area crashed. The airplane came to rest in a small creek. The tailboom and wing had completely separated from the main cabin, except for some of the flight-control cables. Flight control continuity was verified from the left aileron to the right aileron, and from the left flap to the right flap. Flight control continuity could not be verified from the wing or empennage to the cockpit because of impact damage. The fuel tank came to rest upside down in the creek with the filling cap off. The smell of fuel was present on scene. The three-bladed-pusher propeller was attached to the engine and intact. One of the propeller blades had mud on it. In addition, no chordwise scratches, "S" bends, or Leading edge gouges were observed on any of the propeller blades. No preimpact failures or malfunctions were identified during the examination of the wreckage.
Probable cause
Loss of power for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA019
- Event ID
- 20011115X02245
- Case number
- NYC02LA019
- 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: 4fc0cd0e63a7fcee96f26c8a1ea03190eefd91e92959ae49c484b224e3e3c1fe; retrieved 2026-09-20T20:18:43.844Z.