FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08FA265 · Cessna 550

3 Aug 2008 · Reading, PA, United States

Drug Plastics and Glass Cessna 550 · Accident: ground collision during landing

From Heritage Field (PTW) to Reading Regional Airport (Carl A Spaatz Field) (RDG)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's fatalities. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
NYC08FA265
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 Possible conflict
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

Cessna 550

Aircraft type
Cessna 550
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
N827DP
Onboard fatalities
Unknown
Route
From Heritage Field (PTW), Pottstown, PATo Reading Regional Airport (Carl A Spaatz Field) (RDG), Reading, PA
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
Landing · landing roll
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
Ground collision
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

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The air traffic controller, with both ground and local (tower) responsibilities, cleared the accident airplane to land when it was about 8 miles from the runway. Another airplane landed in front of the accident flight, and the controller cleared that pilot to taxi to the hangar. The controller subsequently cleared a tractor with retractable (bat wing) mowers, one on each side, and both in the “up” position, to proceed from the terminal ramp and across the 6,350-foot active runway at an intersection about 2,600 feet from the threshold. The controller then shifted his attention back to the airplane taxiing to its hangar, and did not see the accident airplane land. During the landing rollout, the airplane’s left wing collided with the right side of the tractor when the tractor was “slightly” left of runway centerline. Calculations estimated that the airplane was about 1,000 feet from the collision point when the tractor emerged from the taxiway, and skid marks confirmed that the airplane had been steered to the right to avoid impact. Prior to the crossing attempt, the tractor operator did not scan the runway, and was concentrating on the left side bat wing. Federal Aviation Administration publications do not adequately address the need for ground vehicle operators to visually confirm that active runways/approaches are clear, prior to crossing with air traffic control authorization, thus overlooking an additional means to avoid a collision.

Probable cause

The air traffic controller’s failure to properly monitor the runway environment. Contributing to the accident was the tractor operator’s failure to scan the active runway prior to crossing, and the Federal Aviation Administration’s inadequate emphasis on vehicle operator visual vigilance when crossing active runways with air traffic control clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08FA265
Event ID
20080820X01264
Case number
NYC08FA265
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: f4e754b1404770d261db9ad4798df82fff339b97849bc7886e5a3845ebf110e6; retrieved 2026-09-15T10:04:15.090Z.