FTW93LA046 · Cessna 152
Air Reldan Cessna 152 · Accident: hard landing
From Lakefront Airport (NEW) to Lakefront Airport (NEW)
Event
- NTSB case
- FTW93LA046
- 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
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N4948P
- Operator
- Air Reldan
- Onboard fatalities
- Unknown
- Route
- From Lakefront Airport (NEW)To Lakefront Airport (NEW)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Flare, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A 17 HOUR STUDENT PILOT WAS SCHEDULED FOR ONE HOUR OF SOLO LANDING AND TAKEOFF PRACTICE ON THE AFTERNOON OF HIS INITIAL SOLO FLIGHT. ON HIS FIRST TOUCH AND GO LANDING THE AIRPLANE LANDED HARD AND BOUNCED TWICE BEFORE CONTROL WAS REESTABLISHED BY THE PILOT. IMMEDIATELY FOLLOWING THE TAKEOFF ROLL, THE AIRPLANE BEGAN TO YAW TO THE LEFT. AFTER BECOMING AIRBORNE, THE AIRPLANE WAS OBSERVED TO DROP THE LEFT WING AND INITIATE A TURN TOWARDS A PARALLEL RUNWAY. THE PILOT STATED THAT HE REDUCED POWER IN AN ATTEMPT TO REGAIN CONTROL, LANDING ACROSS THE PARALLEL RUNWAY. THE AIRPLANE NOSED OVER COMING TO REST IN THE INVERTED POSITION. THE RUDDER WAS FOUND STUCK TO THE LEFT AS RESULT OF THE DAMAGE INCURRED BY THE NOSE GEAR DURING THE HARD LANDING.
Probable cause
HARD LANDING DUE TO THE PILOT'S INADEQUATE FLARE. A FACTOR WAS THE BLOCKED RUDDER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA046
- Event ID
- 20001211X16047
- Case number
- FTW93LA046
- 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: 8cf8033ce852ac0f3e2d0d5649966d3a50af936414b2a4e3c5e33191f5ae3ec4; retrieved 2026-09-23T02:27:38.811Z.