FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN05LA118 · Bellanca 8GCBC

14 Jul 2005 · Englewood, CO, United States

Bellanca 8GCBC · Accident: on ground/water collision with object while taxiing

From 1V5 · Boulder, CO to Centennial Airport (APA)

Report a problem

Event

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

Bellanca 8GCBC

Aircraft type
Bellanca 8
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
N5043N
Operator
Unknown
Onboard fatalities
Unknown
Route
From 1V5 · Boulder, COTo Centennial Airport (APA), Englewood, CO
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
Taxi · from runway
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
On ground/water collision with object
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 › Clearance, 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

The pilot was directed by tower to cross taxiway "A" straight onto the ramp where the pilot had a permanent tie-down spot. Because there was a jet being moved at the west-most portion of the open area preceding the ramp, the pilot chose to taxi north through east portion of the open area that was next to the where his tie-down spot was. The pilot said he was taxiing at a normal "fast walking pace" with engine power set at 1,000 rpm. As he approached the north side of the open area, the pilot said he heard a loud banging noise and felt the airplane pitch over on its nose. The pilot said the tires had contacted a helicopter dolly, "causing a sudden stop and pitch-over." The airplane's impact with the dolly caused substantial damage to the bottom fuselage structure and the landing gear strut attach points. The helicopter dolly was a 10-by-10 foot square, 1 foot high, wooden deck. The platform had a metal frame with castered wheels, foot pads, and a "Y-shaped" tow bar. The deck was a natural wood color. The frame around the deck was painted white. The dolly was located at the northwest corner of the TAC Air ramp abeam the A3 taxiway, and approximately 18 feet south of the west to east running yellow taxi stripe that leads from taxiway "A" to the ramp. The pilot said that while taxiing, he was actively scanning for conflicts and noting all aircraft and vehicles in the vicinity. He said never saw the dolly until the airplane struck it. The pilot said about his airplane, "... it has decent forward visibility when in the three-point configuration and normally does not require weaving to be able to see objects off the nose. At only one foot high, completely flat, and neutral in color, the object (helicopter dolly) is quite difficult to spot. The dolly was placed in a common movement area." The area through which the pilot taxied was considered a non-movement area. According to the 2005 Aeronautical Information Manual, non-movement areas are taxiways and apron (ramp) areas not under control of air traffic. Aircraft clearance from other aircraft or objects while taxiing in these areas is the responsiblity of the pilot. FAA inspectors observed a faded "NO TAXI" marking on the non-movement area approximately 30 feet south of the helicopter dolly. The marking was located such that the pilot would have taxied over it before striking the helicopter dolly.

Probable cause

the pilot not maintaining clearance from the portable helipad during taxi after landing resulting in the airplane colliding with it. Factors contributing to the accident were the pilot's selection of a taxi route through a non-movement area, his inability to see the portable helipad, and the helipad.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN05LA118
Event ID
20050803X01152
Case number
DEN05LA118
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: cfad8976e1af2aa41fce162c7cc4337a3ce4942ca0999ed9708ca79de0f28aee; retrieved 2026-09-22T05:39:23.724Z.