SEA99LA166 · Pitts 11
Pitts 11 · Accident: loss of control in flight while maneuvering
From Idaho Falls Regional Airport (IDA) to an unrecorded destination
Event
- NTSB case
- SEA99LA166
- 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
- 1 · 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
Pitts 11
- Aircraft type
- Pitts 11
- 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
- N11PU
- Operator
- Noble, James, K. · private individual
- Onboard fatalities
- Unknown
- Route
- From Idaho Falls Regional Airport (IDA), Idaho Falls, IDTo 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
- Maneuvering
- 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 in flight
- 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
- Stall/spin
- 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
- Pilot in command › Remedial action, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A videotape of the accident showed the aircraft successfully completing a series of two counter-clockwise aileron rolls, immediately followed by two clockwise snap rolls. During the second run of maneuvers, initiated from an approximate altitude of 100-200 feet AGL, the aircraft recovered from the final snap roll in a 90 degree right-wing down, nose low attitude rather than the wings level attitude of the previous maneuver. One to two seconds later, the aircraft returned to a wings-level attitude having lost approximately half of its available altitude. The nose pitched back to a flat attitude and the aircraft impacted the ground. The aircraft's engine was heard to rev on the tape about a second after the impact.
Probable cause
The pilot-in-command's delayed recovery from a snap roll. A contributing factor was the low altitude at which the maneuver was initiated.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA166
- Event ID
- 20001212X19887
- Case number
- SEA99LA166
- 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: 7f742737c8e668627e637ea992dd008c2a909fca2c8a646f659eb760ee10c436; retrieved 2026-09-20T21:47:22.234Z.