FTW95LA046 · Raven S100A
Raven S100A · Accident: hard landing
From Albuquerque, NM (no airport) to an unrecorded destination
Event
- NTSB case
- FTW95LA046
- 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
Raven S100A
- Aircraft type
- Raven S100
- Category
- Balloon
- 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
- N54693
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albuquerque, NM (no airport)To 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
- Landing
- 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 › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER A 6 HOUR FLIGHT, WITH 1 HOUR OF FUEL REMAINING, THE BALLOON PILOT ELECTED TO LAND. HE LANDED WHERE THE TERRAIN WAS STILL RELATIVELY OPEN, AFTER FLIGHT OVER OTHER AREAS THAT WERE SUITABLE FOR LANDING. THE ON-BOARD GLOBAL POSITIONING SYSTEM (GPS) INDICATED THE GROUND SPEED WAS 32 MPH. THE PILOT SAID HE ENCOUNTERED 'SIGNIFICANT WIND SHEAR' DURING THE LANDING APPROACH, AND HE VENTED THE ENVELOPE 50 FEET ABOVE THE GROUND. THE BALLOON TOUCHED DOWN AND WAS DRAGGED ACROSS THE GROUND. THERMAL ACTIVITY CAUSED THE BALLOON TO ASCEND, BUT BECAUSE MOST OF THE HOT AIR HAD BEEN VENTED, IT DESCENDED BACK TO THE GROUND AND LANDED HARD. THE PILOT SAID THE WIND HAD BEEN FORECAST TO REMAIN RELATIVELY CALM THROUGHOUT THE DAY; HOWEVER, AT THE TIME OF THE ACCIDENT, HE ESTIMATED IT TO BE AT 28 KNOTS WITH GUSTS TO 33 KNOTS. THE ACCIDENT SITE WAS ABOUT 107 MILES NORTHEAST OF THE LAUNCH SITE.
Probable cause
THE PILOT'S IMPROPER IN-FLIGHT PLANNING/DECISION. A FACTOR RELATED TO THE ACCIDENT WAS: THE HIGH WIND CONDITION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA046
- Event ID
- 20001206X02599
- Case number
- FTW95LA046
- 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: 2ba5eec06c53513c63dbf3bc8d9e4cb50cb084b66c64e007d58ebe2a4fd432ad; retrieved 2026-09-21T13:32:23.627Z.