FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 2030 · Boeing 757-232

25 Feb 2006 · Boston, MA, United States

Boeing 757-232 · Accident: on ground/water collision with object while standing

From Boston Logan International Airport (BOS) to Southwest Florida International Airport (RSW)

Report a problem

Event

NTSB case
NYC06LA074
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
Airline
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

Boeing 757-232

Aircraft type
Boeing 757
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
N697DL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS), Boston, MATo Southwest Florida International Airport (RSW), Fort Myers, 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 121: Air Carrier
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
Standing · engine(s) not operating
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

  • Driver of vehicle › 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 driver of a deice vehicle, and a ground employee in the bucket of the deice vehicle, were spraying the accident airplane. At the completion of the deice operation, the driver of the deice vehicle began to drive away from the airplane. The ground employee in the bucket of the deice vehicle then observed ice accumulation on the vertical stabilizer. As the driver of the deice vehicle initiated a turn back toward the airplane, the boom of the deice vehicle struck the airplane, resulting in substantial damage to the left elevator.

Probable cause

The deice vehicle driver's failure to maintain clearance from a standing airplane, which resulted in a collision between the deice vehicle and left elevator of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06LA074
Event ID
20060308X00278
Case number
NYC06LA074
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-02-26.
  • API snapshot SHA-256: 6ab042748b5cee9708eba4db1178355ebb41cd9f0e4334a023656ade62f0aa7a; retrieved 2026-09-18T14:55:13.920Z.