NYC03LA013 · Avian Balloon Skyhawk
Avian Balloon Skyhawk · Accident: in flight collision with object during landing
From Cottageville, WV (no airport) to an unrecorded destination
Event
- NTSB case
- NYC03LA013
- 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
Avian Balloon Skyhawk
- Aircraft type
- Avian Balloon SKYHAWK
- 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
- N71AV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cottageville, WV (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
- In flight collision with object
- 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
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
As the balloon was positioned to land at a "selected-predicted" field, the pilot observed power lines in the decent path, and the elected to abort the landing. The pilot fired the main burner, and realized that the balloon would not climb above the power lines. Unable to deflate the balloon or stop the forward momentum, he ordered the passenger to jump from the basket. The pilot secured the fuel system and jumped to the ground. The balloon then struck and slid down the power lines, before descending to the ground. The landing field was about 600 feet in length, with a tree line at the approach end. About 120 feet beyond the tree line, were utility power lines and an electric fence. No obstacles were observed beyond the power lines for the remainder of the field along the balloons flight path. According to the Balloon Flying Handbook (FAA-H-8083-11), "It is usually better to fly over an obstacle and land beyond it than to land in front of it. Over fly powerlines, trees, and water, among other obstacles, on the way to the landing, rather than attempting to land in front of them and risk being dragged into them."
Probable cause
The pilot's improper decision not to over fly the landing area, which resulted in an in-flight collision with power lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA013
- Event ID
- 20021112X05458
- Case number
- NYC03LA013
- 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, coordinates, damage. 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: de18be27796d76dc9a5fa63d3ada3cccd106eee6c86c199fb1f09bee08933f4d; retrieved 2026-09-21T09:33:31.957Z.