AirNow Flight 2352
Embraer EMB-110P1 · Accident: loss of engine power en route
From Bangor International Airport (BGR) to Dillant Hopkins Airport (EEN)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC05FA042
- 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
- 1 · 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Embraer EMB-110P1
- Aircraft type
- Embraer EMB-110
- 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
- N49BA
- Operator
- AirNow
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Bangor International Airport (BGR), Bangor, METo Dillant Hopkins Airport (EEN), Swanzey, NH
- 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 135: Air Taxi & Commuter
- 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
- En route · cruise
- 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
En route to the company's home airport, the twin-engine airplane either experienced a loss of power to the right engine, or the pilot decided to shut the engine down. Although the home airport had night visual meteorological conditions, and there was no evidence of any malfunction with the remaining engine, the pilot opted to fly a night precision instrument approach to an airport 45 nautical miles closer, with a 1-mile visibility and a 100-foot ceiling. Unknown to the pilot, there was also fog at the airport. The pilot did not advise or seek assistance from air traffic control or the company. When the airplane broke out of the clouds, it was not stable. Approaching the runway, at full flaps and exceeding the 25 percent maximum for a go-around, the pilot added full power to the left engine. The high power setting, slow airspeed, and full flaps combination resulted in a minimum control speed (Vmc) roll. No determination could be made as to why the right engine was inoperative, and there were no mechanical or fuel-related anomalies found that would have precluded normal operation.
Probable cause
The pilot's improper decision to attempt a single-engine missed approach with the airplane in a slow airspeed, full flap configuration, which resulted in a minimum control speed (Vmc) roll. Contributing factors included an inoperative engine for undetermined reasons, the pilot's in-flight decision to divert to an airport with low ceilings and visibility while better conditions existed elsewhere, the pilot's failure to advise or seek assistance from air traffic control or his company, and the low cloud ceilings, fog, and night lighting conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05FA042
- Event ID
- 20050124X00092
- Case number
- NYC05FA042
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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 2005-01-14.
- API snapshot SHA-256: 5b87e4c6a697599ffa1c4a7ee0483cbe091205ab7bba802de5d6c74a5b5f88b9; retrieved 2026-09-18T12:59:19.214Z.
- The NTSB's operator name is blank for N49BA; the operator shown is the name the NTSB records it doing business as.