# Incident 20130418006529I: Boeing 737-73V, Lansing, MI, April 18, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 18, 2013, 11:47 local time
- Place: Lansing, MI
- Airport: Capital City
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: Air carrier (Part 121)
- Operator: SCNA
- Location: 42.7325° N, 84.5555° W: Placed by OpenAirDocs: center of Lansing, MI, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.7325&lon=-84.5555&mi=10
- Aircraft: N710SY, a cancelled registration (https://openairdocs.org/deregistered/N710SY-2021-08-21) (OpenAirDocs)
- Registry model: Boeing 737-73V (registry code 1384540, https://openairdocs.org/model/boeing-737-73v) (OpenAirDocs)
- Registry engine: CFM International CFM56-7B20 series (registry code 13042, https://openairdocs.org/engine/cfm-international-cfm56-7b20-series) (OpenAirDocs)
- Reported make and model: BOEING 737-73V
- Reported engine: CFM INTL CFM56-7B20
- People aboard: 85
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 20,000 total, 10,000 in this make and model, 240 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130418006529I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON APRIL 18, 2013 SCNA FLIGHT 266 ENROUTE FROM DCA TO LAN ENCOUNTERED MODERATE CONTINUOUS TURBULENCE WHILE ON APPROACH TO RWY 28L.  WINDS WERE REPORTED BY THE TOWER AS 200 DEGREES AT 16KTS GUSTING TO 28KTS.  AFTER AN ATTEMPT AT LANDING THE CREW INITIATED A GO AROUND AND ELECTED TO REMAIN IN A RIGHT TRAFFIC PATTERN FOR ANOTHER ATTEMPT AT THE VISUAL APPROACH.  WINDS FOR THE SECOND ATTEMPTED LANDING WERE REPORTED BY THE TOWER AS 200 DEGREES AT 17KTS GUSTING TO 27KTS.  THE CREW AGAIN INITIATED A GO AROUND AND ADVISED LAN TOWER THAT THEY WOULD LIKE TO PROCEED TO DTW.  THE CREW THEN DECLARED AN EMERGENCY DUE TO A FLIGHT CONTROL MALFUNCTION.  ENROUTE TO DTW THE CREW NOTED THE YAW DAMPER WAS NOT ENGAGED.  AFTER RESET IT WAS NOTED THE YAW DAMPER DISENGAGED AGAIN.  THE CREW LANDED IN DTW WITHOUT FURTHER INCIDENT AND MADE THE REQUIRED ENTRIES IN THE MAINTENANCE LOGBOOK.  AN INSPECTOR FROM THE DTW FSDO REPORTED SCUFF MARKS AND SEVERAL DEEP CUTS TO THE #4 MAIN TIRE AS WELL AS MUD RESIDUE ON THE INBOARD SIDEWALL OF THE #3 TIRE INDICATING THE AIRCRAFT HAD TOUCHED DOWN AT SOME POINT DURING THE LANDING ATTEMPTS.  NO OTHER DAMAGE WAS OBSERVED.

THE FLIGHT CREW ADDITIONAL TRAINING EMPHASIZED CRM, TRANSFER OF CONTROLS, CHECKLIST USAGE, STABILIZED APPROACH CRITERIA, WINDSHEAR ESCAPE MANEUVER, CROSSWIND LANDINGS WITH FAILED YAW DAMPER, MISSED APPROACH PROCEDURES, EFFECTS OF CROSS CONTROL ON FINAL, YAW DAMPER SYSTEM, SINGLE CHANNEL WARNING SYSTEM ALERTS, SETTING UP FOR PROPER VISUAL PATTERNS. CROSSWIND LIMITATIONS.  THIS TRAINING WAS FAA OBSERVED AND DEEMED SUCCESSFUL.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.