NTSB CAROL · Event
Event OPS12IA303
Registry · N639AE
FAA Aircraft Registry record.
Make / Model
EMBRAER EMB-145LR
Year of manufacture
1999 · 13 years old at event
Engine
ALLISON AE 3007A
Seats / Engines
55 seats · 2 engines
Last airworthiness date
19991023
ADS-B equipped
Yes — Mode-S A85F30
Registrant of record
AMERICAN AIRLINES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The flight's continued operation through an area containing substantial convective weather activity. Contributing to the accident was the air traffic control/traffic management unit's lack of awareness and recognition of the effect of weather movement on the departure route in use and the flight crew's acceptance of a route and limited weather deviation that was inadequate to maintain a safe distance from the thunderstorms in the area.
Factual narrative
On January 24, 2012, at about 1927 Central standard time, American Eagle flight EGF3376 (EGF3376), an Embraer E145LR regional jet, was struck by lightning shortly after departure from Dallas-Fort Worth International Airport. Review of National Weather Service radar data for the area showed the presence of moderate to extreme intensity precipitation along the aircraft's route of flight. Archived lightning data obtained by Safety Board meteorologists after the accident showed that EGF3376 passed through an area of recorded scattered lightning and close to an area of concentrated lightning activity coincident with extreme precipitation just before the crew reported the strike. At the time of the incident, EGF3376 was operating on an instrument flight rules (IFR) flight plan and receiving air traffic control (ATC) services from Fort Worth Air Route Traffic Control Center (ZFW). EGF3376 was a scheduled passenger flight under operating under 14 Code of Federal Regulations part 121 between DFW and Madison, Wisconsin (MSN). Following the lightning strike, the crew declared an emergency and diverted to Little Rock, Arkansas. After landing at Little Rock, the aircraft was inspected and damage was found that required replacement of the left wingtip and left aileron, as well as additional repairs to skin and rivets on the left wing. There were no injuries reported to the 50 passengers and 3 crewmembers. EGF3376 departed DFW airport at 1912 and was given radar vectors toward the "east gate" used for departures from Fort Worth Terminal Radar Approach Control's (D10) airspace. Because of severe weather affecting the entire area, D10's arrival and departure routes to the north and south were closed, and aircraft wishing to proceed toward the northeast were being sent through the east gate via the DFW VORTAC 064 radial or south of that radial. Airspace to the north of the east gate was occupied by arriving traffic. Before being transferred to ZFW, EGF3376 was instructed to proceed direct to NOBLY waypoint, which is on the Maverick (TTT) VORTAC 064 radial. The aircraft first called ZFW sector 83 at 1923, climbing through 12,000 feet for 17,000 feet. The R83 controller recleared the pilot to climb and maintain FL190. About 20 seconds later, the pilot requested a 20 degree left deviation for weather. The R83 controller asked to confirm the request, and the pilot responded, "That's going to take us further away from the weather." The controller approved a ten degree deviation. At 0124, the controller contacted the D10 departure controller, advising, "We're losing the 064 radial – we're going to be shutting off the east gate because they can't stay south of the 064 radial." At 1924:51, EGF3376 asked, "What's the weather look like ahead of us?" The controller replied that there were, "…moderate and heavy precipitation returns until at least north of Texarkana." The pilot then asked, "what about turning left back direct to Dallas?" The controller responded, "okay EGF3376 understand you want to return back to Dallas?" The pilot responded, "yeah… That would get us out of the weather quicker for 3376?" The controller then asked, "EGF3376 understand that you're requesting a clearance back to Dallas-Fort Worth. Is that correct?" At 1925:25, the pilot asked, "how's the weather look that direction for 3376?" The controller replied, "well behind you, I've got moderate precipitation as well and to the south of you." The pilot of EGF3376 then asked, "what about to the north… We are (unintelligible) here." The controller then advised the pilot, "… You cannot go to the north and that's the arrivals in over Bonham (BYP) and they got a bunch of airplanes. I can't let you go that far north." At 1927:38, EGF3376 called the center controller. The controller acknowledged the call, and EGF3376 continued, "yeah were going to go ahead and declare an emergency. We've been hit by lightning and we'd like to divert to Little Rock." The controller immediately cleared EGF3376 direct to the Little Rock airport at flight level 180. He then asked if there was any additional assistance required and the pilot responded "not now." The aircraft was subsequently handled by ZFW sectors 37 and 27 before being handed off to Memphis Center and eventually Little Rock approach, where the aircraft landed without further incident. According to information provided by American Eagle, a post-flight maintenance inspection revealed lightning damage to various components of the left wing. For further information, see the ATC Group Chairman's Factual Report in the docket for this case. A regional jet departed from Dallas-Fort Worth International Airport on a scheduled passenger flight to Madison, Wisconsin. About 15 minutes after takeoff, the crew declared an emergency because the airplane had been struck by lightning and requested to divert to Little Rock, Arkansas. After landing, the airplane was inspected and found to have sustained damage from the lightning strike requiring repairs to the left wing skin and rivets and replacement of the left wingtip and aileron. At the time of the incident, the airplane was being handled by controllers at the Fort Worth Air Traffic Control Center. Significant convective weather was in the area and along the airplane's route, resulting in closures of several routes into and out of the Dallas area. The controllers did not provide specific information on the location of the convective activity along the airplane's route until the crew asked for the information. However, in response to a question, the controllers did advise the crew that there was moderate to heavy precipitation ahead. The crew attempted to identify areas where they could divert to avoid the convective activity, but the controller was unable to approve significant deviations because of other traffic flows in the vicinity. Shortly afterward, the lightning strike occurred. Because of the lightning strike and requests for weather deviations by other aircraft flying through the same area, the center's Traffic Management Unit began rerouting aircraft away from the area and toward other routes less affected by convective weather. When interviewed, traffic management staff noted that this pattern was normal: it was not unusual to wait until pilots refused to fly a route because of weather impact before discontinuing its use. This incident was included as an example in a recommendation letter to the FAA, available at http://www.ntsb.gov/doclib/recletters/2012/A-12-018-020.pdf, which recommends improved transmission of real-time lightning data to both controllers and pilots. 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 Environmental issues-Conditions/weather/phenomena-Convective weather-Thunderstorm-Decision related to condition - C
- F Environmental issues-Conditions/weather/phenomena-Convective weather-Thunderstorm-Awareness of condition - F
- F Personnel issues-Action/decision-Info processing/decision-Identification/recognition-ATC personnel - F
- F Personnel issues-Action/decision-Action-Lack of action-ATC personnel - F
- F Personnel issues-Action/decision-Action-Lack of action-Flight crew - F
Verbatim from NTSB's published report. Source file
NTSB_2012_OPS12IA303.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 (maintenance, thunderstorm). 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)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
Browse the full corpus — academia portal ↗