ERA11CA029 · Squeglia R/Wheeler W HUMMEL BIRD
Squeglia R/Wheeler W HUMMEL BIRD · Accident: abnormal runway contact during landing
From North Perry Airport (HWO) to North Perry Airport (HWO)
Event
- NTSB case
- ERA11CA029
- 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
Squeglia R/Wheeler W HUMMEL BIRD
- Aircraft type
- Squeglia R/wheeler HUMMEL BIRD
- 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
- N824RS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Perry Airport (HWO), Hollywood, FLTo North Perry Airport (HWO), Hollywood, 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he had completed a takeoff and flew the airplane around the traffic pattern without incident. He configured the airplane on a stable approach to runway 09, compensating for a crosswind by positioning the airplane into a left crab angle. As the airplane approached the runway threshold, the pilot applied right rudder and left aileron to align with the runway centerline and prevent drifting to the right. The pilot stated that he over corrected for the crosswind condition and the airplane began to drift to the left. The airplane touched down hard and the left main landing gear bent laterally. As the right main landing gear touched down, the airplane became unstable and veered to the right. The airplane collided with a runway sign, resulting in substantial damage to the right wing and fuselage. The pilot reported that there were no mechanical anomalies with the airplane. The wind reported at the airport about the time of the accident were from 04 degrees at 7 knots.
Probable cause
The pilot's inadequate flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA029
- Event ID
- 20101021X11931
- Case number
- ERA11CA029
- 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, coordinates. 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: 6b6eae2a4b5857d0b299e34f797b11efc52500744c4a865736f4c114a811d8d9; retrieved 2026-09-15T15:30:12.504Z.