# Incident 19960510017219I: Boeing 7373H4, Dallas-Ft Worth, TX, May 10, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 10, 1996, 23:16 local time
- Place: Dallas-Ft Worth, TX
- Airport: Dallas-Fort Worth International
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: Air carrier (Part 121)
- Operator: SWAA
- Location: 32.8309° N, 96.8502° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=32.8309&lon=-96.8502&mi=10
- Aircraft: N315SW, a cancelled registration (https://openairdocs.org/deregistered/N315SW-2012-06-01) (OpenAirDocs)
- Registry model: Boeing 737-3H4 (registry code 138447K, https://openairdocs.org/model/boeing-737-3h4) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: BOEING 7373H4
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 12,000 total, 7,000 in this make and model, 200 in the last 90 days
- NTSB investigation: [NTSB FTW96IA210](https://openairdocs.org/ntsb/FTW96IA210) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960510017219I

## Narrative

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

NARRATIVE: SWA 768 WAS CLEARED TO LAND ON RWY 31L. THE F/O WAS FLYING A VISUAL APPROACH USING THE ILS FOR BACKUP. WHILE OVER THE APPROACH LIGHTS ON SHORT FINAL, THE CREW EXPERIENCED A RAIN SHOWER OF MODERATE INTENSITY VARYING TO HEAVY AS THEY CROSSED THE LANDING THRESHOLD. THE AIRCRAFT DRIFTED LEFT OF CENTERLINE, TOUCHDOWN OCCURRING ON THE LEFT SIDE OF THE RUNWAY. DURING THE LANDING ROLLOUT, THE NOSE GEAR CONTACTED SEVERAL RUNWAY EDGE LIGHTS, BREAKING THEM AND CAUSING FOD DAMAGE TO THE #2 ENGINE. THE LEFT MAIN GEAR DEPARTED THE EDGE OF THE PAVED SURFACE AND TRACKED ACROSS THE UNPAVED GRASS SURFACE ADJACENT TO THE RUNWAY FOR APPROXIMATELY 700' BEFORE THE AIRCRAFT COULD BE STEERED BACK ONTO THE RUNWAY EXIT AND TAXI TO GATE 4C WHERE IT WAS INSPECTED. THE INCIDENT WAS REPORTED TO SWAA DISPATCH CENTER WITHIN THE HOUR AND RELAYED TO APPROPRIATE AGENCIES AS DIRECTED BY COMPANY OPS MANUAL.^PRIVACY DATA OMITTED^ THIS INCIDENT IS CLOSED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB FTW96IA210](https://openairdocs.org/ntsb/FTW96IA210), May 11, 1996: Boeing 737-300 (N315SW), Dallas, TX, incident, minor damage. Probable cause: failure of the pilot to maintain directional control and runway alignment, during the landing roll out. Factors relating to the incident were: darkness, the adverse weather condition, the wet runway,…

## Other reports on N315SW (1)

Matched to the same aircraft by N-number and date.

- [Incident 19900806043129I](https://openairdocs.org/incident/19900806043129I), Aug 6, 1990: Boeing 7373H4 (N315SW), Burbank, CA. APU fire warning with APU shut off. Returned. Fire indicating system checked and cleaned.

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.