N362FX

HISTORY OF FLIGHTOn July 26, 2016, at 1510 central daylight time, an Embraer EMB-505 airplane, N362FX, was substantially damaged when it was involved in an accident near Sugar Land, Texas. The two airline transport pilots sustained minor injuries; the sole passenger was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 corporate/executive flight.

The flight approached Sugar Land Regional Airport (SGR) from the west, and the flight crew was provided radar vectors for the instrument landing system (ILS) approach to runway 35 at SGR. The controller advised the flight crew of “heavy to extreme precipitation” about 1 mile east of the runway extended centerline.

The pilot-in-command reported that he flew the ILS approach to runway 35 and then transitioned to a visual approach. He recalled that light to moderate rain began on final approach about 2 or 3 minutes before landing and commented that it was not the heaviest rain he had ever landed in. The wind was from about 150° at 11 knots (kts) as they crossed the final approach fix. The airplane broke out of the clouds about 600 ft above ground level, and the runway was in sight at that time. The pilot landed “solidly” and started braking promptly; however, the airplane did not seem to slow down.

The airplane was equipped with a flight data recorder (FDR) and a brake control unit (BCU), which captured system-related data. The FDR and BCU data revealed that, during the landing, the main wheels began to spin up about 1509:53, and over the next 1.5 seconds, the left and right main wheel speeds increased to about 50 kts and 90 kts, respectively, before immediately decreasing to about 0 kts and 60 kts, respectively.

About 1509:55, the weight-on-wheels parameter transitioned from air to ground. The airplane touched down about 200 ft beyond the displaced threshold about 128 kts ground speed. Both wing spoilers deployed at that time and remained extended for the duration of the available data. At that time, both wheel speeds began to increase again; however, about 1 second later, the right wheel speed started to decrease for a second time. In response to the decreasing wheel speed, the BCU immediately initiated a prolonged full dump (PFD) to the right wheel, which removed wheel brake pressure in an attempt to recover wheel speed and prevent skidding. The right wheel speed continued to decrease, and at 1509:57.5, the right wheel speed had decayed to 0 kts where it remained for the duration of the data. When the right wheel speed did not recover, the BCU simultaneously initiated an anti-skid-fail CAS message. The pilot recalled that the crew alerting system (CAS) system displayed an anti-skid message during the landing, but he did not recall exactly when. The left wheel speed increased to about 114 kts at 1509:59. However, the left wheel speed decreased again, and the BCU initiated a PFD to the left wheel brake at 1510:01. The left wheel speed subsequently decreased to 0 kts at 1510:02.

At 1510:02, the pilot applied the emergency brake. The airplane ground speed was about 105 kts and about 2,600 ft of runway remained at that time. The pilot released the emergency brake momentarily at 1510:19 before applying it again at 1510:26 for the remainder of the data. Both wheel speeds subsequently decreased to and remained at 0 kts for the remainder of the data except for one short increase about 1510:29.5. About 1510:30, the airplane’s ground speed had decreased to 60 kts; the data ended at 1510:31.2 consistent with the inertia switch removing power from the FDR before the airplane came to a complete stop. The airplane ultimately departed the end of the runway, crossed an airport perimeter road, and encountered a small creek before coming to rest.

The pilot indicated in a postaccident statement that, before the flight, he checked the weather via an online application, as well as Fltplan.com. En route weather data was also available on the airplane’s multifunction display (MFD) and on the pilot’s personal tablet. The radar returns displayed on the MFD were green and yellow, and the returns displayed on the tablet were all green. The pilot stated, however, that he was uncertain whether the depictions were real-time or delayed. The airplane was also equipped with onboard weather radar but it was not turned on during the accident flight because, according to the pilot, the other sources did not indicate severe weather.

AIRCRAFT INFORMATIONThe Pilot’s Operating Handbook (POH) indicated that the unfactored landing distance for an airplane weighing 14,000 lbs with an operative anti-skid system, flaps 3 (landing configuration), a landing reference speed of about 107 kts, and a 10-knot tailwind was about 2,797 ft. The factored landing distance was about 5,367 ft for a wet runway condition and about 5,640 ft for a runway contaminated with 0.125” of standing water. The landing distance data contained in the POH was based on the anti-skid system being operative. The corresponding landing reference speed was about 107 kts.

The main brake system was controlled by a brake-by-wire arrangement. Pilots independently commanded wheel brake pressure to either or both main wheel assemblies via position transducers installed on the rudder pedals. The transducers provided inputs to the BCU, which controlled the wheel brakes control and shutoff valves.

The BCU incorporated locked wheel, antiskid, and touchdown protection. Locked wheel protection was designed to activate when a wheel speed was 30% less the reference velocity. When activated, the BCU reduced brake pressure to the slower wheel to zero allowing the wheel speeds to equalize. Antiskid protection, when activated, reduced brake pressure to recover wheel speed and prevent tire skidding. Touchdown protection prevented brake application until the airplane was on the ground or wheel spin-up occurred regardless of pedal inputs. Prolonged full dump (PFD) logic is initiated when the wheel speeds have not recovered following activation of the antiskid protection. Upon expiration of the PFD, the BCU will provide an antiskid fail CAS message if the wheel speeds have still not recovered. In that situation, wheel braking would remain available; however, brake pressure would need to be modulated directly by the pilot.

The emergency/parking brake, which was operated with a T-handle, which was mechanically linked to the emergency/parking brake valve and allowed the pilot to directly modulate brake pressure. Proper emergency braking consisted of pulling the emergency/parking brake handle with care. Braking would be initiated using very little handle displacement. Anti-skid protection was not available when using the emergency brake, and rapid emergency/parking brake actuation could lead to tire skidding.

In case of an anti-skid failure, the main brakes are to be applied progressively until deceleration is felt and then brake pressure is to be modulated as required. The emergency brake is to be used in the event of a brake failure CAS message.

The airplane was equipped with wing ground spoilers, which automatically deployed on landing.

METEOROLOGICAL INFORMATIONThe prevailing surface wind shifted from northwest to southeasterly about 1501, which was about 9 minutes before the accident. Thunderstorms were present in the vicinity of the airport. An abrupt change in surface wind direction and/or speed is consistent with the local thunderstorm activity. The SGR Automated surface observing system (ASOS) recorded wind, precipitation, and visibility data at one-minute intervals. According to the observations recorded at 1509, 1510 and 1511, the visibility was 3/8-mile in heavy rain. During that time, the two-minute average wind was from 152° to 154° at 10 to 11 knots and the five-second maximum average wind from 151° to 159° at 12 to 16 knots.

The SGR Meteorological Aerodrome Report (METAR) observations indicated that 0.70 inches of rain fell between 1506 and 1517. Based on the one-minute observations, the rainfall rate was between 4.2 and 6.0 inches per hour at the time the airplane was landing. Airport surveillance camera imagery recorded about the time of the accident was consistent with the METAR observations.

The SGR tower controller advised the pilot of changing wind conditions and of better weather conditions west of the airport. However, the controller did not update the pilot regarding visibility along the final approach course or precipitation at the airport.

Airport Information

Airport:

Sugar Land Regional SGR

Runway Surface Type:

Concrete

Airport Elevation:

82 ft msl

Runway Surface Condition:

Wet

AIRPORT INFORMATIONThe Pilot’s Operating Handbook (POH) indicated that the unfactored landing distance for an airplane weighing 14,000 lbs with an operative anti-skid system, flaps 3 (landing configuration), a landing reference speed of about 107 kts, and a 10-knot tailwind was about 2,797 ft. The factored landing distance was about 5,367 ft for a wet runway condition and about 5,640 ft for a runway contaminated with 0.125” of standing water. The landing distance data contained in the POH was based on the anti-skid system being operative. The corresponding landing reference speed was about 107 kts.

The main brake system was controlled by a brake-by-wire arrangement. Pilots independently commanded wheel brake pressure to either or both main wheel assemblies via position transducers installed on the rudder pedals. The transducers provided inputs to the BCU, which controlled the wheel brakes control and shutoff valves.

The BCU incorporated locked wheel, antiskid, and touchdown protection. Locked wheel protection was designed to activate when a wheel speed was 30% less the reference velocity. When activated, the BCU reduced brake pressure to the slower wheel to zero allowing the wheel speeds to equalize. Antiskid protection, when activated, reduced brake pressure to recover wheel speed and prevent tire skidding....