ATL83FA178 · Cessna 150
Consolidated Aviation Cessna 150 · Accident: airframe, component or system failure during takeoff
From 8A4 · Kennesaw, GA to an unrecorded destination
Event
- NTSB case
- ATL83FA178
- 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
Cessna 150
- Aircraft type
- Cessna 150
- 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
- N5835G
- Operator
- Consolidated Aviation
- Onboard fatalities
- Unknown
- Route
- From 8A4 · Kennesaw, GATo 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
- Airframe, component or system failure
- 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
- Substantial
Cause areas
- Pilot in command(cfi) › Checklist, not performed
- Pilot in command(cfi) › Flight controls, improper use of
- Pilot in command(cfi) › Raising of flaps, not obtained
- Pilot in command(cfi) › Stall/spin, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED IN A WOODED AREA AFTER A TOUCH AND GO LANDING. THE WING FLAPS LEVER HAD BEEN PLACED TO THE UP POSITION BUT THE FLAPS DID NOT RETRACT. WHEN THE CFI FINALLY NOTICED THAT THE FLAPS WERE NOT UP HE TOOK OVER AT ABOUT 200 FT AGL AND STARTED A SHALLOW RIGHT TURN. THE AIRSPEED WAS ABOUT 62 MPH INDICATED WHEN THE CFI TURNED LEFT WITH A NOSE HIGH ATTITUDE. THE ACFT STALLED AND SPUN TO THE GROUND ABOUT 600 FT FROM THE DEPARTURE END OF THE RWY. THE FLAP INDICATOR REGISTERED 33 DEGREES. THERE WAS A NOTICE POSTED BELOW THE FLAP INDICATOR WHICH READ 'USE 30 DEGREE FLAP MAX'. INVESTIGATION REVEALED THAT THE FLAP MOTOR FUSE WAS BLOWN. BOTH PLTS HAD BEEN RESTRAINED BY SHOULDER HARNESS SECURED THROUGH INTERIOR PLASTIC MOLDING. AT IMPACT THEY CAME LOOSE. THIS ACFT WAS NOT MANUFACTURED WITH SHOULDER HARNESS. ACFT LOGS DID NOT SHOW WHERE, WHEN OR BY WHOM THE EXISTING HARNESS WAS INSTALLED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FA178
- Event ID
- 20001214X42859
- Case number
- ATL83FA178
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-05-07.
- API snapshot SHA-256: fa1d4ae382395c51294f54aaa91d99cc908832cfdf82b7d6fbeee480ffcf17f2; retrieved 2026-09-21T06:50:12.924Z.