Tuesday, November 11, 2025

Sikorsky UH-60 Black Hawk incident occurred on July 7, 2025, near Ingram, Texas

  • Location: Ingram, TX 
  • Incident Number: CEN25LA242 
  • Date & Time: July 7, 2025, 15:57 Local 
  • Registration: UNREG 
  • Aircraft: Sikorsky UH60 
  • Injuries: 1 None 
  • Flight Conducted Under: Public aircraft

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200494/pdf

On July 7, 2025, about 1557 central daylight time, an unregistered Sikorsky UH-60 Black Hawk helicopter collided with an unregistered DJI Mavic 3T unmanned aerial vehicle (drone) near Ingram, Texas. The UH-60 received substantial damage to the tail rotor system and the Mavic 3T was destroyed. The pilot and occupants of the UH-60 were not injured, and the helicopter made a successful landing. The UH-60 was operated by the National Guard and the Mavic 3T was operated by the Texas Department of Public Safety (DPS), as public use aircraft during flood response operations arising from the July 4, 2025, flooding of the Guadalupe River.

Postaccident inspection of the helicopter by the operator revealed substantial damage to the tail rotor blades.

According to the Texas DPS pilot who was operating the drone. He received instruction on mission plans from the Emergency Operations Center (EOC), that had been set up in response to the flooding in the area. Each drone team consisted of 2 pilots. One pilot would fly the drone, and the other would monitor radio frequencies and visually scan the area. They would receive a mapping mission to fly and once completed they would land the drone and relocate to the next assigned mapping mission. During operations, they would monitor several radio communication frequencies and if other aircraft traffic was heard in their area, they would descend to 50 ft above ground level (agl) and wait until the other aircraft traffic was no longer a factor and then resume their mission.

The drone team was starting a mapping mission that was to fly a programmed grid pattern but were hand flying the drone to the start of the grid pattern. They did not see, nor did they hear any other traffic announce operations or positions in the area, and suddenly lost communication with the drone. After losing communication with the drone, they saw the helicopter make an emergency landing.

The drone pilot reported that that the deconfliction strategy, that was in place at the time of the collision, was verbally passed down, and that drones were to operate at altitudes at or below 200 ft agl, and that manned aircraft would operate no lower than 400 ft agl unless a specific need required going lower.

Cessna 172M Skyhawk, N433PT, accident occurred on October 7, 2025, near Miami, Florida

  • Location: Miami, FL 
  • Accident Number: ERA26LA007 
  • Date & Time: October 7, 2025, 14:50 Local 
  • Registration: N433PT 
  • Aircraft: Cessna 172 
  • Injuries: 1 Minor, 1 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201814/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N433PT

On October 07, 2025, at 1440 eastern daylight time, a Cessna 172M, N433PT, was substantially damaged when it was involved in an accident near Miami, Florida. The private pilot and the flight instructor were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

The flight was an instructional flight for the private pilot to practice commercial pilot maneuvers in preparation for the pilot's commercial check ride. The pilots departed from Miami Executive Airport (TMB), Miami, Florida and proceeded southwest to an area to perform the maneuvers. The pilots reported performing multiple chandelles and an accelerated stall. After completing the accelerated stall, the pilots performed a simulated emergency descent. After recovering about 550 ft above ground level, they began a climb out. The pilots reported that after climbing about 300 ft, the engine started to act “erratically” and there was a loss of about 500 rpm. The pilots stated that the airplane would not climb and then determined that a forced landing would be required. The pilots landed the airplane in a shallow-water area of the Florida Everglades; during the landing, the airplane flipped over.

A postaccident examination of the airplane revealed that it had sustained substantial damage to the left wing, vertical stabilizer, and rudder.

The wreckage was retained for further examination.

Monday, November 10, 2025

Beechcraft B100 King Air, N30HG, fatal accident occurred on November 10, 2025, in Coral Springs, Florida

This is preliminary information, subject to change, and may contain errors. Any errors in this post will be corrected when the preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N30HG

- History of Flight:
On November 10, 2025, at about 1018 local time, a Beechcraft B100 King Air, N30HG, registered to International Air Services Inc Trustee out of Carson City, Nevada, was destroyed when it impacted residential terrain and a man-made pond in Coral Springs, Florida. There were reportedly no survivors. The relief flight originated from Fort Lauderdale-Executive Airport (FXE/KFXE), Florida, and was destined to Montego Bay-Sangster International Airport (MBJ/MKJS), Jamaica.

The purpose of the flight was to deliver supplies to victims of Hurricane Melissa in Jamaica.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data (figure 1), at 1002:56 LT, the airplane was observed taxiing from the parking area towards runway 27. At 1014:12, the airplane departed runway 27 (elevation 11.7 ft) and entered a climbing right to an altitude of 4,200 ft. At 1017:11, after reaching that altitude, the airplane started a right hand turn. It was travelling about 164 knots groundspeed (GS) at that point.  At 1017:52, before the conclusion of the turn, the airplane started a steep descent. At 1018:06, the airplane was observed at 3350 ft, 238 knots groundspeed (GS) and descending 4500 feet per minute (fpm). The airplane continued to descend and accelerated to about 270 knots GS. At the last few seconds, the airplane slowed down to about 260 knots GS while the descent rate continued to increase. The last ADS-B return was recorded about 160 ft from the crash site, the airplane was at 450 ft, 257 knots GS, and descending 14000 feet per minute (fpm).

Figure 1: ADS-B exchange track ran through Flysto

Figure 2: TOC, right turn and final descent ran through Flysto

- Pilot Information:
unknown at this point.

- Airplane Information:
The accident aircraft, serial number BE-14, was manufactured in 1976. It was a twin-turboprop airplane powered by two (Honeywell) Garrett AiResearch TPE-331 engines.

- Wreckage and Impact Information:
The first identified point of impact was a downed palm tree in the backyard of a residential home. This was followed by ground impressions on a 125° heading leading to a destroyed fence. The airplane then continued into the pond and was destroyed by impact forces. The house itself was not damaged. The impact trajectory (speculation) suggests the aircraft was on a steep descent/out of control (see figure 3).

Three videos were released shortly after the writing of this entry, the videos showed the aircraft in a nose down, wings level vertical descent. The ground impressions were as a result of the right wing impacting the ground.

Figure 3: Impact trajectory

Figure 4: Aircraft in descent

Figure 5: Impact trajectory

- Airport Information:
none.

- Weather:
(1) METARs:

METAR KPMP 101453Z 28009KT 10SM SCT025 SCT033 27/22 A3004 RMK AO2 SLP174 6//// T02670217 51017 PNO

METAR KPMP 101511Z 29011G15KT 10SM BKN025 BKN033 28/22 A3004 RMK AO2 T02780222 PNO

METAR KPMP 101524Z 27011KT 10SM SCT024 SCT030 28/22 A3004 RMK AO2 T02780217 PNO

METAR KPMP 101553Z 30013KT 10SM FEW020 BKN027 BKN034 27/22 A3003 RMK AO2 SLP171 T02670217 PNO

METAR KBCT 101454Z 29006G17KT 10SM BKN020 BKN026 BKN038 27/22 A3004 RMK TCU DSNT W-NW CIG LWR W

METAR KBCT 101553Z 30015G21KT 10SM SCT020TCU SCT027 SCT039 27/21 A3004 RMK TCU OHD AND ALQD AND DSNT SW-NW MOV E

METAR KFLL 101453Z 28010G17KT 10SM SCT023 SCT040 BKN120 27/21 A3004 RMK AO2 SLP170 T02670211 51016

METAR KFLL 101553Z 29009G21KT 10SM SCT027 BKN250 28/21 A3003 RMK AO2 SLP166 T02830211

(2) Area Forecast Discussion:

Area Forecast Discussion
National Weather Service Miami FL
644 AM EST Mon Nov 10 2025

...New AVIATION...

.KEY MESSAGES...
Updated at 644 AM EST Mon Nov 10 2025

  - A strong cold front passage today will bringing the coldest
    temperatures of the season so far to the region tonight into
    Tuesday.

  - Strong northwest winds will result in significant wind chill
    values Tuesday morning, especially around the Lake region.

  - Hazardous marine conditions expected to develop across all
    coastal waters starting this morning.

  - Hazardous beach conditions expected today and into Tuesday with
    increasing risk of rip currents for all beaches of South
    Florida, and high surf over the Palm Beach county beaches.

&&

.SHORT TERM...
(Today through Tuesday)
Issued at 206 AM EST Mon Nov 10 2025

Guidance remains in good agreement about the upcoming cold weather
snap starting Monday morning. Latest sfc analyses place the frontal
boundary past the peninsula with the onset of drier and colder air
advection in place. Deep zonal flow will spread across the region
with northerly cold wind bringing the first cooling down of the
season.

Latest forecast temps for this afternoon remain around the same
values from previous model runs with highs in the low-mid 70s around
the Lake region, and in the upper 70s to low 80s further south. The
northerly winds are expected to reach the 10-15 mph range with
higher gusts by the early afternoon hours on Monday, intensifying
the cold air advection during the evening and overnight hours.

Model guidance remain in consensus in having the coldest period of
the cold weather on Tuesday morning, with lows dropping into the
upper 30s to low 40s around the Lake region, and mid-upper 40s
elsewhere. Locations right along the coast may remain close to 50.
In terms of wind chill values, guidance have been going a few
degrees cooler since yesterday`s runs and now NBM is showing 30-32
degrees around the Lake region, with mid 30s to around 40 elsewhere.

A Cold Weather Advisory has been issued for Glades, Hendry, and
northern portions of Palm Beach and Collier counties from 4am to 9am
Tuesday morning for wind chill values of 35 degrees or less. Wind
chill values like those can lead to hypothermia with prolonged
exposure. Use caution while traveling outside. Wear appropriate
clothing, a hat, and gloves. Keep pets indoors as much as possible.
Make frequent checks on older family, friends, and neighbors. Ensure
portable heaters are used correctly. Do not use generators or grills
inside.

For the Tuesday afternoon highs, models also remain consistent with
keeping low-mid 60s around the Lake region/interior areas, and upper
60s elsewhere. Winds will likely peak in intensity, around 15 mph,
during the late morning hours Tuesday then beginning to subside in
the afternoon hours.

&&

.LONG TERM...
(Tuesday night through Sunday)
Issued at 206 AM EST Mon Nov 10 2025

Not much changes for the long term forecast philosophy with the air
mass across the state gradually moderating from Wednesday and
through the end of the work week as the west Atlantic ridge
returns. The last portion of the cold spell will happen Wednesday
morning with lows in the 40s inland, and high 50s to around 60
near the coasts.

Decreasing winds veer to a more easterly flow while warming up the
air mass. Afternoon highs climb back into the upper 70s to low 80s
by Friday and through the upcoming weekend.

POPs remain basically in single digits every day of the forecast
period with benign weather prevailing.

&&

.AVIATION...
(12Z TAFS)
Issued at 644 AM EST Mon Nov 10 2025

Generally VFR prevails at all terminals during the next 24 hours.
Gusty NW winds will begin later this morning and becoming robust
this afternoon. Gusts to around 25 kt may continue into the
evening hours.

&&

.MARINE...
Issued at 206 AM EST Mon Nov 10 2025

Hazardous marine conditions will develop today in the wake of the
frontal passage starting this morning and continuing through the
middle of the work week. All of South Florida`s coastal waters will
be affected by the stronger winds, including the Lake.

A Small Craft Advisory has been issued with latest model estimates
showing possible wave heights in the 10 to 14 feet range in the
Atlantic waters on Tuesday, along with wind speeds in the 25-30 kt
range with higher gusts. Conditions should begin subsiding
Wednesday morning starting on the Gulf waters and then the
Atlantic later that afternoon.

&&

.BEACHES...
Issued at 206 AM EST Mon Nov 10 2025

A high risk of rip currents is in effect for all South Florida
beaches today behind a cold front passage.

A high surf advisory will also be in effect for all Palm Beach
county beaches starting early morning Tuesday, and might be expanded
into Broward and Miami-Dade depending on latest model trends.

&&

.FIRE WEATHER...
Issued at 206 AM EST Mon Nov 10 2025

Northerly flow will result in very dry conditions and increasing
winds expected Tuesday afternoon with RH/wind speed values
approaching critical levels, mainly over the western half of South
Florida. The situation will continue to be closely monitored in case
further action becomes necessary.

- Additional Information:


Figure: Vertical Rate Profile

Sunday, November 09, 2025

Blog Update 2: November 9, 2025

It has been ~3 months since the last blog update, there was a notable increase in the number of views (the total number of views since the start of the blog is roughly 52065), despite this, the comments are sitting on a mere 54, and the followers on 2! I tried crawlers and indexing methods, but I still can't figure out a way to make the blog appear on Chrome (It appears on other search engines like duckduckgo, yahoo, and bing, which are the main feeders to the blog apparently). If you have any ideas on how to fix this, please don't hesitate to contact me!

I've also noted some traffic from online forums and Facebook, I like to lurk on these, but some of them require account log-ins, so I can't see the feedback (for example, Beechtalk, which is the 3rd most traffic source to this blog, and Facebook, which doesn't specify if the traffic came through a public page/group). I would love to hear the feedback from anyone on these sites if possible :P! 

On another note, the FAA ASIAS (Aviation Safety Information Analysis and Sharing) has not been updated since October 2nd due to the US government shutdown, which has effected the accident/incident reporting for the last month and continuing right now.

If you have any suggestions and feedback, please share them in the comments.


Eurocopter EC 130T2 (Airbus Helicopters H130), N107VU, fatal accident occurred on November 8, 2025, near Music City Executive Airport (XNX/KXNX), Gallatin, Tennessee

This is preliminary information, subject to change, and may contain errors. Any errors in this post will be corrected when the preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N107VU

- History of Flight:
On November 8, 2025, at about 1341 local time, an Eurocopter EC 130T2 (also known as the Airbus Helicopters H130), N107VU, was substantially damaged when it was involved in an accident near Lebanon, Tennessee. One occupant sustained fatal injuries, and two occupants sustained serious injuries. The helicopter was registered to Air Methods LLC out of Greenwood Village, Colorado, and being operated by Vanderbilt LifeFlight as a Title 14 Code of Federal Regulations Part 135 air medical flight.

According to preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) data (figure 1), at about 1333, the helicopter departed XNX and entered a climbing right turn towards the south. At 1338, the helicopter was 5.30 miles south of XNX when it entered a 180 turn back north while continuing to climb. At 1339:40, the helicopter was about 3 miles south of the airport when it reached a maximum altitude of 4,200 ft. This was followed by a very steep descent. At about 1340:30, the helicopter was ~1.80 miles south of the airport and travelling ~140 knots groundspeed when it entered a descending right hand turn with an average rate of -4000 feet per minute (fpm). At 1341:18, the last ADS-B return was recorded as the helicopter was at the conclusion of the turn. The helicopter was at 650 ft and had decelerated to about 84 knots GS and -2300 fpm. The accident site was located 700 ft from this data point.

Figure 1: ADS-B exchange data ran through Google Earth Pro

Figure 2: Last portion of flight.

- Pilot Information:
unknown at this point.

- Aircraft Information:
According to the Airbus website:

The H130 is an intermediate single-engine helicopter tailored for passenger transport, sightseeing and VIP duties, as well as medical airlift and surveillance missions. As a multi-role rotorcraft, the H130 has a spacious cabin for a pilot and up to seven passengers. Depending on the configuration, it can carry up to two pilots, one stretcher and three to four medical crewmembers.

Among the H130’s enhancements are an active vibration control system and advanced environmental control; improved air conditioning; a cabin interior structure redesign with a fully flat floor; energy-absorbing seats and integration of a crash-resistant fuel system. A cockpit update for the rotorcraft brings an enhanced human-machine interface through the integration of Garmin’s G500H TXi glass cockpit with a synthetic vision system (SVS) and the helicopter terrain avoidance and warning system (HTAWS). A wireless connection automatically transfers flight data at the end of each mission.

The helicopter was powered by a Safran Arriel 2D turbine engine.

- Wreckage and Impact Information:
The helicopter struck the top of a tree and impacted terrain about 2 miles south of XNX. The helicopter came to rest on its left side and was not consumed by a post crash fire. The helicopter remained mostly intact and sustained substantial impact damage. The tailrotor remained partially attached to the airframe. (figure 3)

Figure 3: Accident site

- Airport Information:
The airport field elevation was 583.3 ft.

- Weather:
The reported weather at 1335 at XNK: variable winds at 5 knots, 10 miles visibility, no clouds under 12,000 ft (CLR), temperature 21°C, dewpoint 14°C, and an altimeter setting of 29.85 inches of mercury.

METAR KXNX 081915Z AUTO 00000KT 10SM CLR 22/15 A2985 RMK A01
METAR KXNX 081935Z AUTO VRB05KT 10SM CLR 21/14 A2985 RMK A01 <<
METAR KXNX 081955Z AUTO 32005KT 10SM CLR 21/14 A2984 RMK A01

Area Forecast Discussion
National Weather Service Nashville TN
1109 AM CST Sat Nov 8 2025

...New AVIATION...

.KEY MESSAGES...
Updated at 1102 AM CST Sat Nov 8 2025

- High probability for a widespread hard freeze Sunday and Monday
  nights. Low to medium chance (30-50%) for light snow
  accumulation across the Plateau early Monday morning.

- Temperatures closer to near-normal values returning by
  Wednesday.

&&

.SHORT TERM...
(Rest of today through Monday Night)
Issued at 1006 AM CST Sat Nov 8 2025

A longwave trough taking shape over the northern Plains and Great
Lakes area is evident on satellite imagery this morning with a
potent cold front currently moving through the Illinois/Missouri
area. For now, conditions are calm across Middle TN. With plenty of
sunshine this afternoon, look for temperatures to warm into the
upper-60s to low-70s. But the aforementioned cold front will make
its presence known as it brings much colder air and gusty northwest
winds. Temperatures will fall overnight and through the day on
Sunday which means that the day`s high temperatures in the 50s will
likely be recorded around midnight. Temperatures during much of the
day on Sunday will only be in the 40s with brisk northwest winds
keeping wind chills in the upper-30s. Temperatures will continue to
free-fall Sunday night with readings below freezing areawide by
midnight and then bottoming out into the 20s early Monday morning.
Coldest period of this event will be Monday and Monday night.
High temperature readings Monday will be in the 30s to near 40
while overnight lows will plummet into the teens to low-20s
areawide.

Meanwhile, this system will also bring a low to medium chance
(~30-50%) of light rain showers mainly north of I-40 tonight and
into Sunday. As temperatures fall, this precipitation will change
to snow by Sunday evening and into at least early Monday morning.
This snow may continue through the day on Monday thanks to
wraparound moisture from a departing low. Any accumulations are
still expected to be light along the Cumberland Plateau, generally
ranging from just a dusting to around a half inch. Models give
around a 40% chance that any accumulations get up to a half inch,
and this would mainly be confined to the typically favored areas
of the Upper Cumberland Plateau like Fentress and Pickett
counties. Regardless, none to little impacts are expected from
this short burst of snow.

&&

.LONG TERM...
(Tuesday through next Saturday)
Issued at 1006 AM CST Sat Nov 8 2025

Temperatures will rebound starting Tuesday with highs making it back
into the 50s and 60s for mid-week and overnight lows above the
freezing mark. Dry northwest flow aloft will persist through much
of next week, helping to keep dry and calm conditions in the
forecast through the end of the week.

&&

.AVIATION...
(18Z TAFS)
Issued at 1102 AM CST Sat Nov 8 2025

Stubborn fog and low stratus continues to erode this morning with
most TAF sites up to VFR at this hour. Improvement will continue
with VFR conditions expected areawide this afternoon. Light winds
are generally out of the south through the remainder of the day,
but will become northwesterly with the arrival of a cold front
between 09Z and 12Z. Winds will strengthen with gusts of 20 to 25
knots through the morning hours. Low clouds will redevelop as
well, bringing areawide MVFR cigs Sunday morning.

- Additional Information:
none.

Saturday, November 08, 2025

Extra EA 300/SC, N330SL, fatal accident occurred on November 8, 2025, at Keystone Heights Airport (42J), Keystone Heights, Florida

This is preliminary information, subject to change, and may contain errors. Any errors in this post will be corrected when the preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N330SL

- History of Flight:
On November 8, 2025, at about 1040 local time, an Extra EA 300/SC, N330SL, registered to Avtech Group LLC out of St. Augustine, FL, was destroyed when it was involved in an accident at Keystone Heights Airport (42J), Keystone Heights, Florida. The sole pilot onboard sustained fatal injuries. The local flight originated from 42J.

Preliminary information indicates the airplane was conducting aerobatic manoeuvres when it entered an inverted spin and lost control.

Preliminary ADS-B data shows that the airplane was flying over the airport at 3,700 ft when it entered a sudden descent to 1,000 ft and disappeared from coverage.

- Pilot Information:
unknown at this point.

- Airplane Information:
The accident aircraft, serial number SC050, was manufactured in 2014. It was a single-seat, low-wing aerobatic monoplane powered by a Lycoming IO-580-X engine rated at 320 hp.

According to the Pilot Operating Handbook (POH):
The plane is designed for acrobatics. Inverted flight maneuvers are limited to max 4 min.

Figure: POH Information

According to section 4.12.3, SPIN:
To enter a spin proceed as follows: 

  • Reduce speed, power idle 
  • When the plane stalls: 
  1. kick rudder to desired spin direction 
  2. hold ailerons neutral 
  3. stick back (positive spinning), Stick forward (negative spinning)

The plane will immediately enter a stable spin. 

  • Ailerons against spin direction will make the spin flatter. 
  • Ailerons into spin direction will lead to a spiral dive. 

Above apply for positive and negative spinning. 

To stop the spin: 

  • Apply opposite rudder 
  • Make sure, power idle 
  • Hold ailerons neutral 
  • Stick to neutral position
After one turn of spinning the plane will recover within about 1/2 turn. 

After six turns of spinning the plane will recover within about 1 turn. 

Recovery can still be improved by feeding in in-spin ailerons. 

N O T E
If ever disorientation should occur during spins (normal or inverted) one method always works to stop the spin: 

  • Power idle 
  • Kick rudder to the heavier side (this will always be against spin direction) 
  • Take hands off the stick The spin will end after 1/2 thru 1 turn. 

The plane will be in a steep dive in a side-slip. Recovery to normal flight can be performed easily. 

N O T E 
After one turn of spinning the altitude loss including recovery is within about 1500 ft. 
After six turns of spinning the altitude loss including recovery is within about 3300 ft.

- Wreckage and Impact Information:
The airplane impacted open flat terrain, came to rest inverted and was consumed by a post crash fire. The main wreckage consisted of the entire airplane, which was confined within one area without a notable debris field. Both wings and tail remained attached to the airframe. It appears that both propeller blades remained attached to the propeller hub, which was still attached to the engine. The impact appears consistent with an inverted flight profile with little to no forward airspeed.

- Airport Information:
Keystone Heights Airport is a non-towered public airport located about 3 miles north of Keystone Heights, Florida. The airport field elevation was 196 ft. The airport features two asphalt runways, runway 5/23 (5046x100 ft) and runway 11/29 (4899x75 ft).

- Weather:
The reported weather at 1035: Winds 180 at 5 knots, visbility 9 miles, a broken cloud layer at 8500 ft, temparture 25°C, dewpoint 19°C, and an altimeter setting of 29.95 inches of mercury

METAR K42J 081515Z AUTO 19004KT 8SM FEW080 FEW090 24/19 A2995 RMK A01
METAR K42J 081535Z AUTO 18005KT 9SM BKN085 25/19 A2995 RMK A01 <<<
METAR K42J 081555Z AUTO VRB04KT 9SM OVC085 25/19 A2994 RMK A01

- Additional Information:
On

Runway excursion: Boeing 737-823 (WL), N991AN, incident occurred on February 10, 2024, at Dallas/Fort Worth International Airport (DFW/KDFW), Dallas, Texas

  • Location: Dallas, Texas 
  • Incident Number: DCA24LA095 
  • Date & Time: February 10, 2024, 19:42 Local 
  • Registration: N991AN 
  • Aircraft: Boeing 737-823 
  • Aircraft Damage: Minor 
  • Defining Event: Runway excursion 
  • Injuries: 104 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/193772/pdf

https://data.ntsb.gov/Docket?ProjectID=193772

On February 10, 2024, about 1942 central standard time, American Airlines flight 1632, a Boeing 737-823, N991AN, experienced a brake system anomaly after landing on runway 17L at the Dallas-Fort Worth International Airport (DFW), Dallas-Fort Worth, Texas. The airplane came to a stop in the paved overrun area beyond the south end of the runway threshold. All 104 passengers and crew members safely evacuated the airplane via airstairs, with no injuries reported. The flight was operated as a scheduled domestic passenger service under the provisions of Title 14 Code of Federal Regulations (CFR) Part 121, traveling from Ronald Reagan Washington National Airport (DCA), Arlington, VA, to DFW in Dallas-Fort Worth, TX.

Analysis:

American Airlines flight 1632 experienced a brake system anomaly shortly after landing on runway 17L at Dallas-Fort Worth International Airport (DFW), Dallas-Fort Worth, Texas. The anomaly resulted in a loss of braking effectiveness that increased the airplane stopping distance. The airplane came to a stop in the paved overrun area beyond the south end of the runway threshold. The crew executed emergency procedures, including engine shutdown and auxiliary power unit (APU) activation, ensuring a safe post-incident response. All 104 passengers and crew members safely evacuated the airplane via airstairs, with no injuries reported. The flight was operated as a scheduled domestic passenger service under the provisions of Title 14 Code of Federal Regulations (CFR) Part 121, traveling from Ronald Reagan Washington National Airport (DCA), Arlington, VA, to DFW.

Each main landing gear (MLG) has a normal braking system powered by hydraulic system B and manually controlled by the flight crew via brake pedals in the flight deck. Pedal movement is transmitted through cables to left and right brake metering valves located in the wheel well, which regulate hydraulic pressure to the respective brake assemblies. Each wheel is equipped with a rotor-stator brake assembly that uses hydraulic pressure to generate braking force.

On February 6, 2024—four days before the incident—American Airlines completed a scheduled modification on the airplane, replacing the original steel brakes with carbon brakes and associated wheel assemblies. This work was performed in accordance with an Engineering Order (EO) and associated cards dated November 2, 2022, based on Boeing Service Bulletin SB 737-32-1429, Revision 4. The modification applied to Boeing 737-800 series airplane equipped with Goodrich or Honeywell steel brakes and wheels. The EO and associated cards included detailed maintenance instructions with sign-off blocks and incorporated the technical content of the Boeing Service Bulletin, supplemented with additional information to ensure compliance with American Airlines’ continuous airworthiness maintenance program.

As part of the conversion to carbon brakes, four flow limiters were installed, replacing the existing bulkhead unions between the rigid hydraulic tubes and flexible hydraulic hoses. Due to the increased length of the flow limiters, the original rigid tubes (four total) located inboard of each MLG within the wing were replaced with shorter ones. Installation required temporary disconnection of each flexible hose, removal of the bulkhead union, installation of the flow limiter, and reconnection of the flexible hose.

Flight data recorder (FDR) data recorded brake pressure from two transducers—one for each side—located upstream of the antiskid valves. These transducers reflect hydraulic pressure supplied by the autobrake system or the pilot-controlled metering valves during manual braking. The recorded values during the incident appeared consistent with expected inputs, indicating no upstream braking system issues. However, the FDR does not record data downstream of the transducers, limiting the ability to evaluate antiskid valve functionality or overall brake system performance. Additional parameters such as wheel speed and brake pressure at the assemblies would enhance investigative capabilities.

The flight crew indicated that they selected an autobrake setting of 3 for the landing at DFW. The autobrake system supplies metered brake pressure to help decelerate and stop the airplane after landing or if a rejected takeoff (RTO) occurs. It monitors airplane deceleration and controls metered pressure to maintain the target deceleration rate selected by the pilot on the AUTO BRAKE select switch until the airplane comes to a full stop, provided there is no flight crew input. Available settings include RTO, OFF, 1, 2, 3, and MAX.

FDR data indicated that both the autobrake system and ground spoilers were functioning at the onset of the landing roll. Upon landing, the increase in the hydraulic brake pressures were consistent with the autobrake setting 3. However, manual brake application by the flight crew likely occurred within seconds of the autobrake application, overriding the autobrake system. The autobrake application discrete parameter confirmed the autobrake was applied for one sample, approximately one second. Once the flight crew’s manual brake application overrode the autobrake, the flight crew controlled the brakes for the remainder of the landing rollout.

According to Boeing, the autobrake system disengages when the metered brake pressure reaches or exceeds 750 pounds per square inch (PSI). During this landing, the right brake pressure increased steadily from 0 to 3000 PSI within four seconds; the left brake pressure increased to 3000 PSI within ten seconds. At the time of autobrake disengagement, the right brake pressure was increasing past 750 psi. This data suggests that a crew member manually applied brakes resulting in the autobrake system disengaging.

Post-incident troubleshooting revealed that the flexible hydraulic hoses connected to the number 3 (right inboard) and number 4 (right outboard) MLG brakes had been improperly reconnected following the carbon brake and flow limiter installation. Specifically, the flexible hydraulic hoses supplying pressure to the number 3 and 4 brakes had been swapped at their connections with the flow limiters (see figure 1).

Further system troubleshooting by American airlines revealed a discrepancy with the wiring to the left MLG wheel speed transducers. During an operational test, maintenance personnel discovered that the wiring harness within the MLG axle had been installed incorrectly. Specifically, the electrical connectors for the number 1 (left outboard) and number 2 (left inboard) wheel speed transducers were swapped.

As a result of these two discrepancies, when a skid occurs, the non-skidding wheel would receive the brake pressure release intended for the wheel on the same MLG that is skidding, and the skidding wheel would receive the (potentially full) metered brake pressure due to its brake not being released. This is because the skidding wheel would receive the antiskid commands intended for the non-skidding wheel, and vice versa.

Given the combination of the switched hydraulic brake hoses and wheel speed transducers, the use of manual braking would not have released the subsequently locked and skidding outboard tires. Eventually, the skidding tires were worn flat until the tires failed. The failed tire would lead to lost braking effectiveness that increased the airplane’s stopping distance beyond the end of the runway.

The investigation confirmed that the only mechanical discrepancies were the reversed hydraulic hoses to the number 3 and number 4 MLG brakes and the reversed wheel speed transducer wires for the number 1 and number 2 MLG wheels.

Safety Actions

American Airlines subsequently revised engineering order card 3222J004-001 adding a step to label the flexible hydraulic hoses prior to removal and requiring an inspector to verify the flexible hydraulic hoses are properly re-installed. In addition, the transducer operational test was incorporated into engineering order card 3222J004-001. This operational test is capable of detecting either swapped flexible hydraulic hoses or swapped transducer connectors.

Additionally, American Airlines issued engineering authorizations (EA) and engineering orders to check the entire B737 fleet for swapped transducer wiring. A total of 50 airplanes were inspected by EA and 253 airplanes were inspected by EO. Of all 303 airplanes inspected, zero were found with transducer wiring swapped. American Airlines also revised their B737NG and MAX aircraft maintenance manuals (AMMs) to enhance the transducer operational test and the main landing gear installation job card has been updated with enhanced steps to ensure the transducer wires are not crossed.

Following the incident, Boeing added Information Notice 02 to service bulletin 737-32-1429 Revision 4. This notice was distributed to alert operators to the risk of crossing hydraulic hoses when reconnecting the flexible hydraulic hoses to the new flow limiters. The notice emphasizes that each flexible hydraulic hose must be reconnected to its corresponding flow limiter and that hoses must not be crossed at any point along their length. Improper reconnection – such as attaching a flexible hydraulic hose to the incorrect flow limiter – will result in incorrect antiskid system operation, potentially leading to a loss of braking action and/or tire failure.

Additionally, Boeing has issued two Fleet Team Digests - 737MAX-FTD-32-24002 and 737NG-FTD-32-24001 - to provide both interim actions as well as final actions to B737NG and B737MAX operators. The interim actions include a list of best practices such as

o Temporarily labeling flexible hydraulic hoses to the corresponding brake positions,

o Labeling wiring harnesses when disconnecting wheel speed transducers, and

o Functional checks to verify flexible hydraulic hoses and transducer wiring is correctly connected. 

The final actions include revising specific AMM tasks and service bulletins where improper maintenance may occur. Boeing released Service Bulletin 737-32-1429 Revision 5 on August 14, 2025. Furthermore, Boeing issued SB 737-32A1599 on October 14, 2025, to ensure proper hydraulic routing following the implementation of service bulletins that alter brake configurations.

The NTSB has investigated several aircraft incidents and accidents that have been the result of cross wiring of wheel speed transducers, all were the result of maintenance human error.

- Probable Cause: Improper maintenance due to human error during a braking system modification diminished braking performance. Contributing to the diminished braking performance was the lack of a functional check to verify the flexible hydraulic hoses and transducer wiring were connected correctly after the braking system modification.