ERA12FA387 · Phillips William L CHALLENGER
Phillips William L CHALLENGER · Accident: loss of control in flight on approach
From Blackwater Creek Ultralightport (9FD2) to Blackwater Creek Ultralightport (9FD2)
Event
- NTSB case
- ERA12FA387
- 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
Phillips William L CHALLENGER
- Aircraft type
- Phillips William CHALLENGER
- 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
- N2571T
- Operator
- Phillips William L
- Onboard fatalities
- Unknown
- Route
- From Blackwater Creek Ultralightport (9FD2), Plant City, FLTo Blackwater Creek Ultralightport (9FD2), Plant City, 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 pattern final
- 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
- Loss of control in flight
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the airport manager, the purpose of the flight was for the pilot/owner to get “one last flight” in the airplane before he sold it. The pilot had experienced health issues and undergone surgery in the years prior to the accident, and had not flown the airplane in about 1 year. The manager watched the entire flight and described the takeoff as “normal.” The first landing approach was “fast and long,” and the pilot performed a go-around and entered the traffic pattern for a second approach. The manager and other witnesses stated that the airplane descended on the base leg of the traffic pattern to about 500 feet, and that the airplane turned and aligned with the runway. During the descent on final approach, the airplane pitched up, leveled off, descended, and pitched up multiple times with corresponding changes in engine power. The airplane “wandered” to the west and was briefly flying parallel to the runway as it headed toward the witnesses on the grass apron and the hangars on the west side of the field. The airplane then pitched up, the nose dropped, and the airplane impacted the ground in a nose-down attitude of about 25-30 degrees. During the descent and at ground contact, the engine was running “at cruise power,” according to the airport manager. The engine continued to run after the accident, and first responders had to pull one of the carburetors from its mount in order to stop the engine. The 79 year-old pilot/owner had never obtained a pilot certificate. Over the 60 years that he documented his flight time, the pilot reported 122 total flight hours. The accident airplane was purchased almost 20 years before the accident but was not registered until 5 years before the accident. At the time of the accident, the airplane had accumulated 19 total airframe hours.
Probable cause
The non-certificated pilot’s loss of control during approach and landing. Contributing to the accident was the pilot’s lack of both total and recent flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA387
- Event ID
- 20120609X22931
- Case number
- ERA12FA387
- 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: ef62dd3c476ec02646c779a7ee9c7f2c02ddf4543ce52c0d96f51072b7dc9575; retrieved 2026-09-13T22:25:52.693Z.