NTSB CAROL · Event
Event ERA14IA249
Registry · N116WA
FAA Aircraft Registry record.
Make / Model
EMBRAER EMB-110P1
Year of manufacture
1982 · 32 years old at event
Engine
P&W CANADA PT6A-60A (1050 hp)
Seats / Engines
20 seats · 2 engines
Last airworthiness date
19820511
ADS-B equipped
Yes — Mode-S A04472
Registrant of record
TVPX AIRCRAFT SOLUTIONS INC TRUSTEE
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inadequate preflight inspection, which resulted in a total loss of engine power due to fuel exhaustion.
Factual narrative
On May 21, 2014, about 0733 eastern daylight time, an Embraer EMB-110P1, N116WA, experienced a total loss of engine power while in cruise flight. The pilot subsequently made an emergency landing at Warren-Sugarbush Airport (0B7), Warren, Vermont. The commercial pilot was not injured and the airplane sustained minor damage to the left wing flap. The airplane was registered to Piper East, Inc and was operated by Wiggins Airways Inc as Wiggins Airways Cargo Flight 1042, under the provisions of Title 14 Code of Federal Regulations Part 135 as a cargo flight. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed for the flight that had departed Manchester International Airport (MHT), Manchester, New Hampshire about 0700 with an intended destination of Burlington International Airport (BTV), Burlington, Vermont.The pilot reported to personnel with the Vermont Aeronautics division that the "normal procedure" for refueling was that the pilot leaves a fuel order the night prior and that 1,000 pounds per side was "their standard fuel load for this run." He had not observed the fuel upload. During the morning preflight check, he observed the fuel indicators showing about 1,000 pounds per side. While in cruise flight at 8,000 feet above mean sea level, about 10 miles south of 0B7, the fuel low pressure light-boost pump fail light illuminated. Subsequently, the right engine "shutdown" and then the left engine "shutdown." He declared an emergency and selected "nearest airport" on the airplane's gps. However, the nearest airport with a runway greater than 3000 feet in length, a limitation set in the gps, was beyond the airplane's glide capability. He subsequently noticed 0B7 about 5 miles away and began to set up for the approach to the runway. Immediately upon touchdown he utilized "aggressive braking" and the left tire deflated, the airplane veered to the left, the left main landing gear departed the paved portion of the runway, and subsequently the right tire deflated. According to a Vermont Aeronautics investigator, tire skid marks began about 475 feet after the runway threshold, the left main landing gear departed the paved portion of the runway 942 feet past the initial tire skid marks, and the airplane came to rest 1,509 feet past the initial tire skid marks, with 590 feet of runway remaining. Examination of the fuel tanks utilizing both the airplane's fuel gauges in the cockpit and the dripless stick method revealed that both fuel tanks were devoid of fuel. There was no evidence noted of any fuel leak or staining and the fuel caps were secure and in place. According to a Federal Aviation Administration (FAA) inspector, the airplane was last fueled on May 13, 2014. Since that refueling, the airplane had flown 1.9 flight hours and consumed about 1,200 pounds of fuel. Also during the time from the last refueling and the incident, maintenance personnel performed multiple engine performance runs and two taxi repositions. One maintenance technician reported to the FAA inspector that during an engine run on May 17, 2014, he noted approximately 500 pounds of total fuel on board. No refueling records were located after the May 13, 2014 refueling and before the incident flight. Subsequently, following the incident maintenance personnel performed a fuel quantity accuracy test and no abnormalities or malfunctions were noted with the fuel quantity indication system. According to the pilot, 1,000 lbs of fuel was to be added to each fuel tank the night before the incident flight. The next morning, he conducted a preflight inspection and reported seeing 1,000 lbs per side and then departed the home base airport on the cargo flight. The pilot reported that, while in cruise flight, the fuel low-pressure light illuminated, followed shortly thereafter by the right engine and then the left engine shutting down. The pilot subsequently diverted the flight to a nearby airport. Upon touchdown, the pilot used "aggressive braking." The left tire subsequently deflated, the airplane veered left, the left main landing gear departed the paved portion of the runway, and then the right tire deflated. Following the incident, maintenance personnel conducted a fuel quantity gauge accuracy test, and no abnormalities or malfunctions were noted that would have precluded normal operation. Postincident examination of the fuel system revealed that the fuel tanks were devoid of fuel. The fuel caps were found secure and in place, and no evidence of any preaccident mechanical malfunction or failure was found. There was no evidence of any fuel staining or leakage. A review of the airplane's fueling records revealed that it was last refueled over a week before the incident; it was not fueled the night before the incident as requested by the pilot. During that week, the airplane was flown about 1.9 flight hours; 1,100 lbs of fuel remained after that flight. Maintenance personnel subsequently conducted multiple engine performance runs and two taxi repositions, which consumed about 600 lbs of fuel, leaving about 500 lbs of fuel, which was also reported by a maintenance technician after the most recent test run before the flight. Given the lack of any preexisting mechanical anomalies and that no fuel was recovered from the airplane, it is likely that the engine lost power due to fuel exhaustion because of the pilot's inadequate preflight inspection. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-Inspection-Preflight inspection-Pilot - C
- C Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level - C
Verbatim from NTSB's published report. Source file
NTSB_2014_ERA14IA249.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗