# Incident 20111020025619I: Embraer-Empresa Brasileira De ERJ 170-200 LR, Hillsborough, NJ, October 20, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 20, 2011, 10:22 local time
- Place: Hillsborough, NJ
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: Air carrier (Part 121)
- Operator: UHLA
- Location: 40.5081° N, 74.6529° W: Placed by OpenAirDocs: center of Hillsborough, NJ, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.5081&lon=-74.6529&mi=10
- Aircraft: N213JQ, registered now (https://openairdocs.org/aircraft/N213JQ) (OpenAirDocs)
- Registry model: Embraer-Empresa Brasileira De ERJ 170-200 LR (registry code 3260121, https://openairdocs.org/model/embraer-empresa-brasileira-de-erj-170-200-lr) (OpenAirDocs)
- Registry engine: GE CF34-8E5 (registry code 30061, https://openairdocs.org/engine/ge-cf34-8e5) (OpenAirDocs)
- Reported make and model: EMBRAER-EMPRESA BRASILEIRA DE ERJ 170-200 LR
- Reported engine: GE CF34-8E5
- People aboard: 69
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111020025619I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE ROOT CAUSE OF THIS INCIDENT RESULTING IN AN AIRCRAFT ROUTE DEVIATION (WITH NO LOSS OF SEPARATION) WAS THE FLIGHTCREW'S INABILITY TO IDENTIFY AND TO FLY THE REVISED HIGH ALTITUDE JET AIRWAY ROUTING THAT BECAME EFFECTIVE ON THE DATE OF THIS INCIDENT.  THE FLIGHTCREW REFERRED TO A CURRENT, BUT INCORRECT NAVIGATION CHART PRODUCED BY JEPPESSEN AND PROVIDED BY THE COMPANY AS PRIMARY FOR NAVIGATION.THIS CHARTING ERROR COMBINED WITH THE AIRCRAFT'S FLIGHT MANAGEMENT SYSTEM (FMS) DEFERRAL DID NOT PROVIDE THE FLIGHTCREW AN OPPORTUNITY TO ACCURATELY IDENTIFY THE REDEFINED JET AIRWAY AND SUBSEQUENTLY NAVIGATE ALONG THE CLEARED ROUTE.  IF THE FMS HAD BEEN USABLE ON THE DATE OF THE INCIDENT, THE VALID ELECTRONIC DATABASE WOULD HAVE PROVIDED THE FLIGHTCREW WITH THE CORRECT AIRWAY ROUTING AND SUBSEQUENTLY ALLOWED THE CREW TO NAVIGATE ALONG THE REDEFINED JET AIRWAY.  FURTHERMORE, EVENTHOUGH THE FLIGHTCREW FOLLOWED STATED PROCEDURES PERTAINING TO MEL PROVISIONS FOR THIS DEFERRAL, MEL PROVISIONS AS CURRENTLY WRITTEN ARE INADEQUATE TO PREVENT RECURRENCE OF A SIMILAR INCIDENT.  THEREFORE, THE COMPANY IS CURRENTLY EVALUATING BOTH DISPATCH SYSTEM / MEL PROVISIONS FOR RISK IDENTIFICATION AND MITIGATION.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.