ERA09CA332 · Teratorn TIERRA II
Teratorn TIERRA II · Accident: collision during takeoff/landing during initial climb
From Cutchogue, NY to Mattituck Airport (21N)
Narrative check · The NTSB narrative appears to contradict this record's registration. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA09CA332
- 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
- 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
Teratorn TIERRA II
- Aircraft type
- Teratorn TIERRA
- 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
- Unregister Narrative disagrees
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cutchogue, NYTo Mattituck Airport (21N), Mattituck, NY
- 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
- Defining eventThe 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft power plant
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he recently installed a newly rebuilt engine in his unregistered experimental amateur-built airplane and completed a 1-hour break-in procedure the day prior to the accident. He was departing from a soft field and he believed that the engine got wet or that the propeller was damaged by mud or rocks during the takeoff, reducing thrust. The airplane gained only 40 to 50 feet of altitude before it impacted trees. The airplane incurred substantial damage to the empennage. The reason for loss of engine power was not determined. The pilot stated he should have taken the airplane back to his home base and not attempted the takeoff from the soft field.
Probable cause
The pilot's decision to attempt takeoff from unsuitable terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA332
- Event ID
- 20090609X11907
- Case number
- ERA09CA332
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 9efd944a3991b5595945d0a117165c9c44da3a0c9dbe3248c1cf200d4c14c41d; retrieved 2026-09-15T11:20:53.594Z.