FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA033 · Taylorcraft BC12-D

22 Nov 2004 · Cocoa Beach, FL, United States

Taylorcraft BC12-D · Accident: in flight collision with terrain/water while maneuvering

From Merritt Island Airport (KCOI) to Cocoa Beach, FL

Report a problem

Event

NTSB case
MIA05LA033
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

Taylorcraft BC12-D

Aircraft type
Taylorcraft BC12
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
N44263
Operator
Unknown
Onboard fatalities
Unknown
Route
From Merritt Island Airport (KCOI), Merritt Island, FLTo Cocoa 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
Maneuvering
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 terrain/water
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

  • Pilot in command › Altitude, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A witness stated that he observed the airplane flying east of his location. The airplane was flying from north to the south at about 400 to 500 feet. The engine sounded like it had "no power" but he could hear the propeller turning. The airplane then flew out of his visual range. A few minutes later, the airplane returned approximately along the same flight path heading south again, but at an altitude of approximately 200 to 300 feet. The airplane engine was still "quiet" and it sounded like it was "throttled back". The airplane made a "hard" banking turn to the left just after it passed west of a stadium and descended out of sight while on a easterly heading. Another witness stated that she first observed the airplane flying from south to north almost directly overhead and just east of her position. The airplane was "fairly low, slow, and quiet", but noted that it was "level", and did not appear to be having any problems. After about five minutes she noticed the airplane flying back from the north to the south. Soon after that she then observed the airplane heading from west to east over the ball field and was "coming down". The airplane hit the ground, "bounced", and then crashed into a fence on the east side of the field. The FAA inspector who responded to the accident stated that there was fuel present in the fuel tanks. The airplane's engine was removed and transported to a facility for an operational test run of the engine under FAA oversight. The airplane engine ran normally, and was capable of developing sufficient power. There was no evidence of any pre-existing mechanical malfunction or failure to the airplane, airplane's systems and engine. Review of the accident airplane's maintenance records indicated the last annual inspection was on October 15, 2003. The airplane had accumulated about 4/10 of an hour since that time. The airplane was three weeks past due for an annual inspection. The FAA determined the accident airplane was not airworthy at the time of the accident. The pilot's FAA medical records indicated that the pilot held a special third class medical issued on 6/8/2004, with a Federal Air Surgeon approval after the pilot had an examiner deferral for further evaluation. The FAA Aerospace Medical Certification Division issued a special issuance authorization letter on 9/1/2004, after review of the airmen's medical records by division medical personnel. The special third class medical was valid until 6/30/2005.

Probable cause

The pilot's failure to maintain altitude resulting in flight collision with ground and subsequent collision with fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA033
Event ID
20041203X01917
Case number
MIA05LA033
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: d2905ae8f3a6e92c8e7083589df26a65ca9c131c1ae28abeb7515add55cec64b; retrieved 2026-09-21T09:10:39.766Z.