FTW02LA014 · Aerostar Raven S57-A
Aerostar Raven S57-A · Accident: in flight encounter with weather en route
From Albuquerque, NM to an unrecorded destination
Event
- NTSB case
- FTW02LA014
- 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
- Unknown
- 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
Aerostar Raven S57-A
- Aircraft type
- Aerostar RAVEN S57-A
- 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
- N3636Z
- Operator
- Bradley S. Rice · private individual
- Onboard fatalities
- Unknown
- Route
- From Albuquerque, NMTo 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
- En route · cruise
- 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
- In flight encounter with weather
- 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
- Utility pole
- 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 › Flight into adverse weather, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot intended for the flight to be short; however, after takeoff, the wind increased and the balloon over flew the intended landing area. The pilot then selected a field at a school in which to land. The field had wires along its edge. As the balloon was clearing the wires, the pilot vented the balloon, but the balloon continued to float past the field, impacting a wooden telephone post located near a building. The balloon rotated, struck the building, and came to rest with its basket on a fence. The pilot reported that at the time of the accident, the wind had increased to approximately 30 knots with gusts to 35 knots. A weather reporting station located approximately 7 miles southeast of the accident site reported the wind speed at 10 knots.
Probable cause
inadvertent flight into adverse (high wind) weather conditions, which resulted in an inflight collision with objects while landing. A contributing factor was the high wind weather condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA014
- Event ID
- 20011025X02146
- Case number
- FTW02LA014
- 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: 4dfb5c2efa18314af03f62778b7dfab7f85e8b95e1e6cad3ea750d2a8ba351e1; retrieved 2026-09-21T09:46:40.683Z.