OpenAirDocs.org

20201229018709I

Incident · No damage
Open the Markdown

FAA incident report · Boeing 737-4H6 · Omaha, NE · December 29, 2020

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
December 29, 2020 · 08:45 local
Place
Omaha, NE
Airport
Eppley Airfield
Phase of flight
Landing: Rollout
Operating rules
Air carrier (Part 121)
Operator
MASA
Damage
No damage
Aircraft
N305GT
Reported as
Boeing 737-4H6
Reported engine
CFM International CFM56-3C1
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
Pilot’s flight hours
12,000 total160 in this make and model160 in the last 90 days
N305GTRegistration cancelled Jan 27, 2025 · Boeing 737-4H6S/N 27674 · Built 1997Airframe modelBoeing 737-4H6Engine modelCFM International CFM56-3C1Turbo-fan

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

? CA is a current B737 line check airman

? Both CA and fo have low time in type at 160 and 40 hours respectively ? But highly experienced aviators otherwise.

? Ficon 3/3/3 braking action reporting ?fair? 70% ¼? Dry snow

? 8500? Runway w/ planned and briefed exit at end of runway taxiway

? Landed with appropriate settings of flaps 30 and autobrakes 3

? privacy data omitted Airbus was landing behind them.

? Damage to 3 taxiway edge lights

? No found damage to aircraft

? CA stated braking action was ?good? On initial touchdown which may have led to a false sense of runway conditions.

? CA stated he believed he was at an appropriate taxi speed prior to turn off.

? Airport manager interview said ?broom team? Manager stated that he believed privacy data omitted was traveling too fast given the conditions prior to the turn off.

? CA stated he may have felt pressure to exit the runway quickly based on privacy data omitted landing behind them, but he was still focused on safety and if they went around it would not be an issue.

? CA reported event to ATC and reported braking action on turn off as ?poor.?

As the FAA filed it

? CA IS A CURRENT B737 LINE CHECK AIRMAN

? BOTH CA AND FO HAVE LOW TIME IN TYPE AT 160 AND 40 HOURS RESPECTIVELY ? BUT HIGHLY EXPERIENCED AVIATORS OTHERWISE.

? FICON 3/3/3 BRAKING ACTION REPORTING ?FAIR? 70% ¼? DRY SNOW

? 8500? RUNWAY W/ PLANNED AND BRIEFED EXIT AT END OF RUNWAY TAXIWAY

? LANDED WITH APPROPRIATE SETTINGS OF FLAPS 30 AND AUTOBRAKES 3

? ^PRIVACY DATA OMITTED^ AIRBUS WAS LANDING BEHIND THEM.

? DAMAGE TO 3 TAXIWAY EDGE LIGHTS

? NO FOUND DAMAGE TO AIRCRAFT

? CA STATED BRAKING ACTION WAS ?GOOD? ON INITIAL TOUCHDOWN WHICH MAY HAVE LED TO A FALSE SENSE OF RUNWAY CONDITIONS.

? CA STATED HE BELIEVED HE WAS AT AN APPROPRIATE TAXI SPEED PRIOR TO TURN OFF.

? AIRPORT MANAGER INTERVIEW SAID ?BROOM TEAM? MANAGER STATED THAT HE BELIEVED ^PRIVACY DATA OMITTED^ WAS TRAVELING TOO FAST GIVEN THE CONDITIONS PRIOR TO THE TURN OFF.

? CA STATED HE MAY HAVE FELT PRESSURE TO EXIT THE RUNWAY QUICKLY BASED ON ^PRIVACY DATA OMITTED^ LANDING BEHIND THEM, BUT HE WAS STILL FOCUSED ON SAFETY AND IF THEY WENT AROUND IT WOULD NOT BE AN ISSUE.

? CA REPORTED EVENT TO ATC AND REPORTED BRAKING ACTION ON TURN OFF AS ?POOR.?