FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA353 · Hawker Beechcraft Corp G36

12 Sept 2024 · Lafayette, LA, United States

Regal Air Partners II Hawker Beechcraft Corp G36 · Accident: fire/smoke (non-impact) during initial climb

From an unrecorded airport to Jack Edwards National Airport (JKA)

Report a problem

Event

NTSB case
CEN24FA353
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
Ongoing
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

Hawker Beechcraft Corp G36

Aircraft type
Beechcraft 36
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
N643RS
Onboard fatalities
Unknown
Route
From not recordedTo Jack Edwards National Airport (JKA), Gulf Shores, AL
Aircraft age
About 16 years (built 2008)
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
Defining eventThe 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
Fire/smoke (non-impact)
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On September 12, 2024, about 1137 central daylight time, a Hawker Beechcraft G36 airplane, N643RS, was destroyed when it was involved in an accident near Lafayette, Louisiana. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The airplane had just departed from runway 4R at the Lafayette Regional Airport (LFT), Lafayette, Louisiana. Automatic Dependent Surveillance-Broadcast (ADS-B) data showed that the airplane lifted off the runway and achieved an altitude of about 200 ft above ground level (agl) by the time it reached the departure end of the runway. The airplane then made a slight left turn followed by a right turn before the data ended. The final recorded altitude was 25 ft agl and the last recorded location was about 450 ft from the accident location. The airplane impacted a golf course about 2,000 ft and 15 degrees from the departure end of runway 4R.

Figure 1. A 3-dimensional representation of the airplane’s flight path. Witnesses reported seeing the airplane during the takeoff and reported seeing thick white smoke trailing from the airplane. A surveillance video from LFT showed the airplane as it began its takeoff and white smoke could be seen trailing from the airplane in the video. The airplane came to rest on a golf course fairway. There were broken tree limbs near the initial impact location. The wreckage debris path was oriented about 60 degree magnetic heading. The wreckage damage was consistent with a right-wing, nose-low impact. The wreckage debris path was about 150 ft from the initial ground scar to the resting pace of the main wreckage. Fire consumed the majority of the fuselage cabin and inboard portions of both wings. The aft fuselage cone and tail surfaces were rotated about 90 degrees to the left. The vertical tail and right horizontal stabilizer remained attached to the aft fuselage. The left horizontal stabilizer was partially separated and folded beneath the aft fuselage. The elevators and rudder were still attached to their respective fixed surfaces. Remains of both wings were located in their appropriate position relative to the fuselage remains. No evidence of an in-flight failure was noted. Both ailerons remained attached to the wings. The left flap was still attached to the wing. The right flap was almost completely consumed by the fire but the inboard portion remained attached to the wing. The airplane’s flight control system was examined and no evidence of a flight control malfunction was found. The cabin section of the airplane was consumed by fire. Evidence of fire was found on the forward side of the firewall with burning and melting of components adjacent to the firewall. The engine did not exhibit the same degree of fire damage as the remainder of the airplane and was retained for further examination.

Figure 2. An image of the airplane wreckage at the accident site.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN24FA353
Event ID
20240912195110
Case number
CEN24FA353
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 73c023f4e80b076b204ac47c2e964882a05490d929c262136783a1c51eaa973f; retrieved 2026-09-15T08:58:04.432Z.