Tuesday, February 12, 2019

Hawker Beechcraft 400A, N750TA: Incident occurred February 11, 2019 at Richmond Municipal Airport (KRID), Wayne County, Indiana

Federal Aviation Administration / Flight Standards District Office; Indianapolis, Indiana

Slid off the runway.

Premier Beechcraft LLC


Date: 11-FEB-19
Time: 16:10:00Z
Regis#: N750TA
Aircraft Make: RAYTHEON
Aircraft Model: 400A
Event Type: INCIDENT
Highest Injury: NONE
Aircraft Missing: No
Flight Phase: LANDING (LDG)
Operation: 91

RICHMOND, Indiana — A chartered plane landing at Richmond Municipal Airport skidded off a snow-covered runway through an airport field and across Ind. 227.

The plane partially pushed through a fence that borders a neighboring farm field.

A pilot, co-pilot and passenger were not injured, according to Rodney Mayse, the airport manager. They all left the airport soon after the accident.

Mayse said the Federal Aviation Administration was investigating the incident, which he said was a first in his 22 years at the airport.

According to flight plans on Flightaware.com, the chartered plane left Waukesha County Airport in Waukesha, Wisconsin, for the trip to Richmond, landing at 10:03 a.m. The plane was scheduled to fly from Richmond to South Bend and return to Waukesha from South Bend later Monday.

According to online information from the FAA, the plane is a Hawker Beechcraft 400A manufactured in 1999 by the Raytheon Aircraft Company. It is registered to Premier Beechcraft LLC in Brookfield, Wisconsin, which is west of Milwaukee.

The plane was landing on a runway that crosses south of the airport buildings and runs southwest. Mayse said the plane overshot a runway that did have snow on it. Even with dense fog, tracks from the plane's tires could be seen in the snow on the runway, then leading through a field. The tracks curved to the left in the field up to the roadway. A gouge mark crossed the roadway to the west shoulder, where more tracks led to the plane's resting place.

A sawed off fence post hung in the air near the nose of the plane, which rested on the ground, as the plane continued to face southwest. 

The plane's left wing blocked the southbound lane of 227. At first, just that lane was closed by law enforcement; however, all of 227 was closed when wreckers arrived to remove the plane. Because the plane blocked traffic, it was permitted to be removed from its resting place; however, the process was a long one.

Mayse said the plane was finally cleared from 227 about 3:15 p.m., and at that time, work continued to taxi the plane back to an airport hangar.

Original article can be found here ➤ https://www.pal-item.com


Anonymous said...

That's a heck of an excursion. Bad judgement considering the runway condition, should have aborted the second he saw a white runway surface. *Increase landing distance 115% for wet or slippery runway.

Anonymous said...

That's going to be an expensive mishap. Glad no one got hurt. Tough when you have to fly in conditions like that.

Anonymous said...

Great pictures leave the guess work out of this incident ! Slippery runway and obviously not enough of it .

Anonymous said...

I have no idea what the performance numbers were for this plane landing on this runway in these conditions or the length of the runway and it's slope for that matter. Based on that there is no way to determine if this amounted to "bad Judgement" of not. Jets land on runways in this condition all the time without problems. Additionally we have no way of knowing if there was a mechanical problem as well. Different limitations are applicable to different pilots based on their experience. What may appear as suicidal to one pilot may be no big deal to a more experienced crew. FWIW, this is probably not a wet/slippery runway scenario (115%) from a performance point of view. It's more likely a contaminated runway performance problem. The level of contamination determines the performance penalty. If this were a performance calculation I were required to perform I would expect to see a solution that would would support a runway long enough to provide a minimum landing distance 2.7 - 3.0 times the normal clean and dry landing distance. And, I'd better make sure I was on speed over the threshold with a touchdown in the TD zone, with otherwise near perfect technique throughout the rollout.
It will all come out in the investigation. Bummer for sure. Glad no one hurt.

Anonymous said...

That previous comment was a mouthful... Remember the old saying...How do you know when there is a pilot in the room??.. Within 30 seconds of entering they will tell you! :-) I would be willing to bet that when that airplane started sliding and taking out fence posts that the pilot himself may have figured that landing there was poor judgement...

CJ Driver said...

Flight Aware shows this aircraft landing at 10:06 EST. (15:06Z)

METAR KRID 111455Z AUTO 08004KT 1/2SM FG SCT003 OVC015 00/00
A3012 RMK AO2=

Anonymous said...

"That previous comment was a mouthful... Remember the old saying...How do you know when there is a pilot in the room??.. Within 30 seconds of entering they will tell you! :-) "

No different than your comment except that his displayed some intelligence.