MIA98LA190 · Aviat A-1A
Aviat A-1A · Accident: loss of control in flight during initial climb
From 44J to an unrecorded destination
Event
- NTSB case
- MIA98LA190
- 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
Aviat A-1A
- Aircraft type
- Aviat A-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
- N32HU
- Operator
- John F. Cullen · private individual
- Onboard fatalities
- Unknown
- Route
- From 44JTo 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
- Initial climb
- 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
- 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 › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot-in-command (PIC) was demonstrating a short field takeoff to a pilot/passenger. It was determined that the rear seat pilot was the PIC and responsible for the aircraft, and the front seat occupant, was a passenger, and was following through on the controls during the demonstration of the short field takeoff. Both pilots agreed the taxi out and run up were normal and performed by the pilot in the front seat. Takeoff was also normal for a short field takeoff until about 50 feet. The front seat pilot said, '...within seconds we had lifted off and were climbing at an unbelievable angle...I remember being awe struck by the pitch angle...the attitude of the airplane was so high that I felt uncomfortable...within a few seconds the nose of the aircraft began swinging to the left and as it did, it fell and I realized we were in a deep stall. As the nose came down [the PIC] yelled, 'I got it, I got it, I got it!'...we rolled slowly back and forth as we were settling towards the ground...we hit the ground hard in almost a flat attitude.' The PIC said, he told the front seat pilot to 'lower the nose' and tried to 'ease the stick forward.' He yelled, 'I have the airplane,' and pushed with both hand on the stick. It would not move and he said it felt like '...I was pushing on a spring.' He released his left shoulder harness in an attempt to get the attention of the pilot in the front seat. Just as he had loosened the left shoulder harness the airplane 'stalled.' He said he brought up the left wing and pushed the nose down. At this point the airplane was 'sinking in a deep stall' when he pushed the nose forward, and flared the aircraft just before touchdown with a 'very high sink rate.' He said he 'believed' the power was cut when the aircraft was 'stalled...[but he] did not have time to look inside the aircraft to determine any accurate throttle position....' In addition, it was his opinion that he 'should not have loosened' his shoulder harness and he 'should not have allowed' the other pilot to fly from the front seat on his first takeoff in this airplane, no matter what his previous experience in other aircraft had been. Ground witnesses observed the airplane pitch up approximately 25 to 30 degrees and climb to an altitude of 100 to 125 feet. The left wing dropped, the airplane pitched forward, struck the left side of the runway, 500 feet from the departure end, on the right cowling and right main landing gear, spun on the nose, ending up 100 feet from the runway centerline, pointing towards departure point. Examination of the airframe and engine did not reveal any discrepancies. Confirmation of the position of the airplane's controls, immediately after the accident, could not be determine, because the airplane was removed from the crash site before it could be examined
Probable cause
The pilot's failure to maintain airspeed, which resulted in a stall. A contributing factor was the pilot's delay in initiating remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA190
- Event ID
- 20001211X10388
- Case number
- MIA98LA190
- 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: e2518bbadab1883ed5c041cc26cb6d6b8285a401459f454f2c7a663f440a7c38; retrieved 2026-09-21T11:27:34.665Z.