MIA06CA029 · Piper PA-34-200
Phoenix East Aviation Piper PA-34-200 · Accident: dragged wing, rotor, pod, float or tail/skid on approach
From Daytona Beach International Airport (KDAB) to Daytona Beach International Airport (KDAB)
Event
- NTSB case
- MIA06CA029
- 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
Piper PA-34-200
- Aircraft type
- Piper PA-34
- 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
- N56825
- Operator
- Phoenix East Aviation
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (KDAB), Daytona Beach, FLTo Daytona Beach International Airport (KDAB), Daytona Beach, 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
- Approach · VFR go-around
- 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
- Dragged wing, rotor, pod, float or tail/skid
- 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
- Dual student › Go-around, improper
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student stated that during the practice single engine approach, the airplane's descent rate was greater then he anticipated and the airplane touched down early. He said that his flight instructor, sitting in the right seat, instructed him to execute a go-around, and during the go-around he only advanced the throttle for the right engine. The instructor said that the student touched down during the landing flare, but continued to flare causing the airplane to become airborne again. Prior to gaining control, the instructor said the student advanced the throttle for the right engine only, causing the left wingtip to strike the runway. The flight crew stated that prior to the accident there were no mechanical failures or malfunctions to the airplane or any of its systems.
Probable cause
The flight instructor's inadequate supervision, and the student pilot's improper go-around procedures, which resulted in the airplane's left wing striking the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA06CA029
- Event ID
- 20060105X00007
- Case number
- MIA06CA029
- 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: 61af71484927f6b871e642e67e75fb96ae26ab2c92120e0c83f8d3cbb96b505f; retrieved 2026-09-22T05:12:17.475Z.