IAD96LA145 · Dickmann PITTS S-1
Dickmann PITTS S-1 · Accident: loss of control on ground/water during takeoff
From Emperor Nicholas II Murmansk Airport (MMK) to an unrecorded destination
Event
- NTSB case
- IAD96LA145
- 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
Dickmann PITTS S-1
- Aircraft type
- Dickmann PITTS S-1
- 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
- N27DD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Emperor Nicholas II Murmansk Airport (MMK)To 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
- Takeoff · roll/run
- 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 control on ground/water
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Estimated position: the centre of Meriden, CT, the place the record names. Not the accident site.
NTSB narrative
There were no witnesses to the accident. The pilot stated that he made 'S' turns as he taxied to the runway. He said that he taxied onto the runway without stopping and added full power to get the tail of the airplane airborne as soon as possible. He stated that the tail got airborne, and before he knew it, the airplane was headed toward trees, which were 100 feet to the left of the runway. The pilot stated that he was not sure if he was airborne, but felt he must have been, and he could have made a successful takeoff, if the trees had not been there. The pilot stated that he corrected back to the right, and the airplane's right wing hit the ground. The pilot did not remember what happened after the right wing hit the ground. The airplane came to rest upright on its main landing gear with the engine separated from the airframe and lodged between the ground and the lower right wing.
Probable cause
failure of the pilot to maintain control of the airplane during take off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96LA145
- Event ID
- 20001208X06754
- Case number
- IAD96LA145
- 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: 9b9a9cb77c7ce2931bc12724f25b2cca27b28942d1962cffbb5990d38bc2dea9; retrieved 2026-09-21T12:28:21.131Z.