LAX93LA326 · Pilatus B4-PC11AF
Pilatus B4-PC11AF · Accident: airframe, component or system failure during initial climb
From Juwata International Airport / Suharnoko Harbani AFB (TRK) to Juwata International Airport / Suharnoko Harbani AFB (TRK)
Event
- NTSB case
- LAX93LA326
- 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
Pilatus B4-PC11AF
- Aircraft type
- Pilatus B4
- Category
- Glider
- 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
- N205AS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Juwata International Airport / Suharnoko Harbani AFB (TRK)To Juwata International Airport / Suharnoko Harbani AFB (TRK)
- 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
- 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
- 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 › Aircraft preflight, inadequate
- Pilot in command › Airspeed, not maintained
Approximate · Estimated position: the centre of Truckee, CA, the place the record names. Not the accident site.
NTSB narrative
THE PILOT FAILED TO DISCOVER A FRAYED TOW RELEASE CABLE DURING THE PREFLIGHT CHECK. THE CABLE WAS BINDING WHEN THE PILOT ATTEMPTED TO ABORT HIS TAKEOFF. THE PILOT INADVERTENTLY STALLED THE GLIDER AND IMPACTED THE RUNWAY SURFACE IN A NOSE DOWN, RIGHT WING LOW ATTITUDE.
Probable cause
FAILURE OF THE PILOT TO CONDUCT ADEQUATE PREFLIGHT CHECKS WHICH RESULTED IN THE GLIDER TAKING OFF WITH A FRAYED RELEASE HOOK CABLE, THE PILOT'S FAILURE TO MAINTAIN AIRSPEED, AND THE INADVERTENT STALL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA326
- Event ID
- 20001211X13178
- Case number
- LAX93LA326
- 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: f4511c74bdcef9a63ca8bf054c08687afa534d9c24a338a6a04426038af7f13f; retrieved 2026-09-21T14:11:06.380Z.