ATL87FKG01 · Jere L. Rosser RAND KR-2
Jere L. Rosser RAND KR-2 · Accident: loss of engine power during initial climb
From 8A4 · Kennesaw, GA to 84A · Marietta, GA
Event
- NTSB case
- ATL87FKG01
- 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
Jere L. Rosser RAND KR-2
- Aircraft type
- Jere L Rosser RAND KR-2
- 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
- N47JJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 8A4 · Kennesaw, GATo 84A · Marietta, GA
- 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 engine power
- 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; Tree(s)
- 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 › Aircraft handling, improper
- Pilot in command › Stall/spin, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING INITIAL CLIMB THE AIRCRAFT WAS OBSERVED AT A HIGH ANGLE OF ATTACK AT LOW ALTITUDE BEFORE DESCENDING IN A STALL/SPIN COLLISION WITH THE GROUND. WITNESSES AT THE APRT REPORTED THAT THE ENGINE SOUNDED ROUGH DURING THE TAXI AND TAKEOFF ROLL. THE PLT HAD RECENTLY PURCHASED THE EXPERIMENTAL HOMEBUILT ACFT AND SEVERAL WEEKS BEFORE THE ACCIDENT HAD ATTEMPTED TO LAND THE TAIL-WHEEL ACFT FOR THE FIRST TIME. THE PLT HAD NO PRIOR TAIL-WHEEL EXPERIENCE. THE ACFT GROUND LOOPED CAUSING SUBSTANTIAL LANDING GEAR DAMAGE AND SUDDEN STOPPAGE OF THE ENGINE. THERE WAS NO RECORDED MAINTENANCE PERFORMED ON THE ENGINE SINCE THE INCIDENT. THE ACCIDENT FLIGHT WAS THE FIRST FLIGHT ON THE ACFT SINCE THE INCIDENT AND THE PLT'S SECOND FLIGHT IN THE ACFT. THE CAUSE OF THE LOSS OF POWER WAS NOT DETERMINED. THERE WAS NO EVIDENCE OF CONTROL SYSTEM MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL87FKG01
- Event ID
- 20001213X34911
- Case number
- ATL87FKG01
- 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: 049c3d973267f8bf1f29862af3e4430fbe0d9528098751c3e4f776f9dea01632; retrieved 2026-09-21T04:21:46.967Z.