NYC00LA151 · Meadows PITTS SPECIAL S-1 PITTS SPEC
Meadows PITTS SPECIAL S-1 PITTS SPEC · Accident: loss of control on ground/water during landing
From Danbury Municipal Airport (DXR) to Emperor Nicholas II Murmansk Airport (MMK)
Event
- NTSB case
- NYC00LA151
- 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
Meadows PITTS SPECIAL S-1 PITTS SPEC
- Aircraft type
- Meadows PITTS SPECIAL 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
- N63DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo Emperor Nicholas II Murmansk Airport (MMK)
- 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
- Landing · landing roll
- 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 › Remedial action, improper
Approximate · Estimated position: the centre of Meriden, CT, the place the record names. Not the accident site.
NTSB narrative
After touchdown, the tailwheel-equipped airplane was on the left side of the runway, so the pilot applied right rudder. The airplane then veered to the right, so the pilot applied left rudder. The airplane continued to the right, so the pilot applied, then locked the brakes while the airplane was still traveling about 30 miles per hour. The airplane flipped over its nose, and onto its back. Winds, around the time of the accident, were calm.
Probable cause
The pilot's loss of control of the airplane during the landing roll, due to his locking of the brakes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA151
- Event ID
- 20001212X21303
- Case number
- NYC00LA151
- 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: 7f206640d118f0ab2021e58c4322ffac719820359c4da4020bb312e49304eed2; retrieved 2026-09-22T12:50:15.203Z.