MIA02LA085 · Grote Cruiser TR-4
Grote Cruiser TR-4 · Accident: in flight collision with object en route
From Miami Executive Airport (TMB) to North Perry Airport (HWO)
Event
- NTSB case
- MIA02LA085
- 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
- 1 · 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
Grote Cruiser TR-4
- Aircraft type
- Grote CRUISER TR-4
- 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
- N98WG
- Operator
- Andrew P. Holub · private individual
- Onboard fatalities
- Unknown
- Route
- From Miami Executive Airport (TMB), Kendall, FLTo North Perry Airport (HWO), Pembroke Pines, 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
- En route · climb to 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 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, static
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not obtained
- Pilot in command › Go-around, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight was cleared for a straight-in approach to runway 9R, from about 10 miles west of the airport, and the pilot was told to report 1 mile out. On the first approach the pilot started to go around just before the arrival end of the runway threshold. The pilot was cleared by the ATC Tower, for "right traffic," and return for a landing on runway 9R. On the second attempted landing witnesses saw the airplane touchdown past midfield and abort the landing. The airplane stayed low to the ground just above the trees, made a left turn toward the north, and started descending behind the trees. The airplane impacted with power lines about 100 feet above the ground and came to rest in the front yard of a private residence about 1 mile east of the airport. There was no post crash fire nor was there any evidence found to indicate a fire in the engine assembly. The examination of the engine assembly and the testing of the fuel pump, throttle/fuel metering unit, and the 6-fuel injector nozzles, revealed no discrepancies.
Probable cause
the pilot-in-command delayed initiating a go-around and failed to obtain sufficient altitude to clear obstacles at the departure end of the airport which resulted in an in-flight collision with power lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02LA085
- Event ID
- 20020419X00554
- Case number
- MIA02LA085
- 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. 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: ceb038283a35d3bfa029e1a91ea9806e5573f53c9d8839487930820f68862a14; retrieved 2026-09-20T20:02:49.873Z.