FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 4514 · Embraer EMB-135LR

24 Jul 2006 · Newark, NJ, United States

Embraer EMB-135LR · Accident during pushback

From Newark Liberty International Airport (EWR) to Boston Logan International Airport (BOS)

Report a problem

Event

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

Embraer EMB-135LR

Aircraft type
Embraer EMB-135
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
N703MR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Newark Liberty International Airport (EWR), Newark, NJTo Boston Logan International Airport (BOS), Boston, MA
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
Pushback/towing
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
Miscellaneous/other
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 › Procedures/directives, not followed

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

NTSB narrative

During pushback, the airplane skidded approximately 14 inches, and sustained damage to the forward pressure bulkhead, forward longerons, and nose landing gear. Both flightcrew reported that the parking brake was released prior to pushback; however, review of the cockpit voice recorder did not reveal any reference to the parking brake being released. In addition, the captain and guideperson used non-standard phraseology when discussing the pushback. A larger and more powerful tug was used for pushback, rather than the preferred tugs for regional jet aircraft. The make and model tug used for the pushback was approved, with caution, at stations where a preferred tug was not available, such as the accident station on the day of the accident.

Probable cause

The captain's failure to follow company procedures, which resulted in pushback with the parking brake set. A factor was the larger than preferred tug.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06LA191
Event ID
20060808X01112
Case number
NYC06LA191
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: 025d8e3a305d8d95c2439efa2eea4722d967e014e4e1a1224c894126e07a0860; retrieved 2026-09-18T14:51:36.696Z.