ERA11LA028 · Brown Thomas E THORP T-18
Brown Thomas E THORP T-18 · Accident: collision with terrain/object (non-CFIT) during landing
From Earle Airpark (13FA) to Thunderbird Air Park (2FA5)
Event
- NTSB case
- ERA11LA028
- 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
Brown Thomas E THORP T-18
- Aircraft type
- Brown Thomas THORP T-18
- 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
- N33TB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Earle Airpark (13FA), Hastings, FLTo Thunderbird Air Park (2FA5), Lake Como, FL
- 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 · landing roll
- Defining eventThe 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
- Collision with terrain/object (non-CFIT)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, as the airplane was landing the wind shifted from a headwind to a tailwind. He elected not to perform a go-around due to power lines and trees located at the end of the runway. The airplane departed the end of the runway and struck fence posts with both wings. The pilot stated that an earlier decision to go around would have prevented this accident. He further reported that there were no preimpact mechanical malfunctions or failures of the airplane. A review of recorded surface observations at airports within an approximate 50-mile radius of the airport revealed that the wind direction was variable from the west to the southeast. Some airports recorded thunderstorm and rain showers in their respective vicinity, indicating frontal passage in the area of the accident airport around the time of the accident.
Probable cause
The pilot's delayed decision to execute a go-around while landing with variable wind, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA028
- Event ID
- 20101021X83850
- Case number
- ERA11LA028
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 144e09d8b910a796216b3d8fa22175260d8943d62b913dfb4c9ca98ad81c0ff5; retrieved 2026-09-15T15:30:18.727Z.