Not Specified Embraer EMB 145XR incident
Embraer EMB 145XR and Boeing 737 824 · Incident: air traffic event during takeoff
Event
- NTSB case
- OPS14IA005
- 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
- Incident
- 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
- Event fatalities
- Unknown
- 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
Aircraft 1 · Embraer EMB 145XR
- Aircraft type
- Embraer EMB-145
- 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
- N11176
- Operator
- Not Specified
- Onboard fatalities
- Unknown
- Route
- From Newark Liberty International Airport (EWR), Newark, NJTo Frederick W. Smith International Airport (MEM), Memphis, TN
- Aircraft age
- About 10 years (built 2004)
- 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
- Takeoff
- 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
- Air traffic event
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Aircraft 2 · Boeing 737 824
- Aircraft type
- Boeing 737
- 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
- N77520
- Operator
- Not Specified
- Onboard fatalities
- Unknown
- Route
- From San Francisco International Airport (SFO), San Francisco, CATo Newark Liberty International Airport (EWR), Newark, NJ
- Aircraft age
- About 4 years (built 2010)
- 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
- Approach · IFR missed approach
- 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
- Near midair/TCAS alert/loss of separation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A near midair collision occurred at Newark Liberty International Airport (EWR), Newark, New Jersey, when an Embraer ERJ145 departing from runway 4R passed in close proximity to a Boeing 737-800 arriving to land on runway 29. Both aircraft were on regularly scheduled Title 14 Code of Federal Regulations Part 121 passenger flights and under control of the EWR airport traffic control tower (ATCT) at the time of the incident. Neither aircraft sustained damage, and no passengers or crewmembers sustained injuries.
The Boeing 737 pilot contacted the ATCT while on the visual approach to runway 29. The local controller instructed the pilot to follow a Boeing 717 ahead and then cleared the pilot to land on runway 29. When the Boeing 717 was on short final, the local controller instructed the Embraer pilot to line up and wait on runway 4R. After the Boeing 717 crossed runway 4R, the local controller cleared the Embraer for takeoff. At that time, the Boeing 737 was about 3 miles from the runway 29 threshold; however, the Embraer did not actually begin its takeoff roll until the Boeing 737 was about 1 mile from the runway 29 threshold at 200 ft. The local controller recognized that the spacing between the Boeing 737 and the Embraer was insufficient and instructed the Boeing 737 pilot to go around. The Embraer continued its takeoff. The controller then provided traffic advisories to both the Boeing 737 and Embraer pilots and instructed the Embraer pilot to maintain visual separation from the Boeing 737. The Boeing 737 subsequently overflew the Embraer at the intersection of runways 29 and 4R. According to recorded Federal Aviation Administration radar data, the closest lateral and vertical proximity between the airplanes was about 0.03 mile and 400 ft, respectively, which is less than the minimum separation requirements for aircraft operating on intersecting runways.
Probable cause
The local controller’s failure to comply with Federal Aviation Administration separation requirements for aircraft operating on intersecting runways.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS14IA005
- Event ID
- 20140425X84104
- Case number
- OPS14IA005
- 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, coordinates, damage. 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: bb4ce856826be5cf2f02cc58acd9b72053a1c7030df7d5c0a15874d8de566488; retrieved 2026-09-13T18:23:07.646Z.