NTSB CAROL · Event
Event ATL95IA043
Aircraft involved
Probable cause & findings
THE INADEQUATE INSPECTION OF THE AIRCRAFT BY OTHER MAINTENANCE PERSONNEL, IN THAT THEY DID NOT PROPERLY DIAGNOSE DISCREPANCIES IN THE ANTISKID BRAKING SYSTEM.
Factual narrative
HISTORY OF FLIGHT
On January 19, 1995, at 0940 eastern standard time, a Boeing 737-247, N4515W, overran runway 9R at the Hartsfield Atlanta International Airport, in Atlanta, Georgia. There were no injuries to the airline transport captain and first officer, the three flight attendants, and the 23 passengers. The aircraft had minor damage. Flight 312 was operated under the provisions of 14 CFR Part 121 by Air South, Inc. Instrument meteorological conditions existed at the time, and an instrument flight rules flight plan was in effect for the scheduled, domestic, passenger flight. The flight originated in Columbia, South Carolina at 0850. The captain stated the following: the engine start, taxi, and takeoff from Columbia were "ops normal." There were no unusual aircraft logbook entries; nothing pertaining to the brakes, anti-skid system, hydraulics, etc. The brakes seemed to perform normally on the ground in Columbia. There were no abnormal gauge indications, nor any warning or caution lights during the entire flight. The instrument landing system (ILS) approach and touchdown to runway 9R were normal. The first officer was the flying pilot. The ILS was manually flown, and the aircraft broke out of the weather at about 500 feet above ground level. The computed approach speed was in the mid-130 knot range. Following a normal approach (no glide path deviations were noted), the aircraft touched down about 1,500 to 2,000 feet down the runway, about 120 knots. The first officer reported that he began to apply wheel brakes about 80 to 90 knots. He remarked to the captain that the anti-skid system seemed to be "releasing." Thrust reverser operation was normal in all respects. The captain took control of the airplane, and checked the brakes. Brake pedal pressure was initially felt, then the brake pedals could be pressed all the way to the floor, and no braking action was observed. The aircraft departed the paved surface at the departure end of the runway. The aircraft came to a stop on the grass, about 200 feet beyond the edge of the departure end threshold. The captain stated that there were never any cockpit indications indicating brake or hydraulic system problems during the landing roll. The captain did not feel that the aircraft had been hydroplaning, and in his opinion, the runway was dry. The first officer described the runway as having "damp spots."
PERSONNEL INFORMATION
Information of the captain is contained in this report at the section titled "First Pilot Information." Copies of his training records are included as an attachment to this report. Information on the first officer is contained in this report at Supplement E. Copies of his training records are included as an attachment to this report.
AIRCRAFT INFORMATION
According to Air South personnel, the aircraft had been recently acquired, and had been in operation for about 35 hours (44 cycles) since Air South's acquisition. The aircraft underwent maintenance work at AAR Oklahoma, Inc. prior to its acceptance by Air South. According to non-routine forms provided by the operator, on January 5, 1995, a ground test of the anti-skid control system was performed in accordance with the Boeing 737 Maintenance Manual Chapter 32-42-0. On January 6, 1995, the left hand inboard and outboard anti-skid control valves were found to be inoperative. They were replaced and operationally checked. According to maintenance records, the only subsequent work performed on the anti-skid system occurred on January 11, 1995. On that day, the left main landing gear anti-skid harness was resecured, following a writeup indicating that it needed to be secured. This work was performed by the operator.
METEOROLOGICAL INFORMATION
Instrument meteorological conditions existed at the time of the incident. Additional information is located at the section titled "Weather Information."
FLIGHT RECORDERS
The cockpit voice recorder (CVR) and digital flight data recorder (DFDR) were secured following the incident, and forwarded to the NTSB Headquarters in Washington, DC for examination. An initial readout of the CVR revealed that the unit had not been disabled by the flight crew, thus it continued operating after the aircraft had come to a stop. No useful information was obtained from the recording. The DFDR data for this incident indicate that the airplane touched down at 132 knots indicated airspeed (IAS), at a pressure altitude of 931 feet, and a magnetic heading of 95 degrees. The data indicate two possible times where the aircraft overran the runway. Assuming a runway length of 9,000 feet, the DFDR data indicated that the airplane touched down either 2,501 or 2,273 feet from the runway 9R approach end. For additional information, refer to the "Digital Flight Data Recorder Study", attached to this report.
WRECKAGE AND IMPACT INFORMATION
The only verified damage to the aircraft was a blown main tire on the left, outboard position. The other three main tires remained intact and inflated, except there was evidence of skidding on the right, outboard tire. The tread of the right, outboard tire showed evidence of rubber reversion. There were skid marks on the runway surface, leading to the tracks in the mud made by the aircraft. An examination of the track which led to the right, outboard tire showed that it had a "steam cleaned" appearance, i.e. it was lighter in color than the surrounding runway surface.
TESTS AND RESEARCH
Following the incident, several tests and examinations were performed. An inspection of the aircraft after the incident revealed that the left, inboard anti-skid valve brake and return lines were crossed. Also, after the aircraft had been returned to service, abnormal main tire wear was observed at the left, outboard position. Further inspection revealed that the wiring to the left, inboard and left, outboard wheel speed transducers were crossed. This discrepancy was corrected, and no further reports of abnormal tire wear were received, or observed. All four main tires, as well as their respective wheel and brake assemblies, were shipped to Thompson Aerospace, Inc., in Miami, Florida. A functional test of each brake assembly was conducted; all operated normally. Brake wear was not greater than 50 percent on any brake assembly. The anti-skid control unit, and the number two anti-skid control valve were removed from the incident aircraft. These units were shipped to Aircraft Braking Systems Corporation for testing and examination. Functional testing of the anti-skid valve revealed that it was functional. Testing of the anti-skid control unit (box) revealed that the left, inboard skid detect circuit was inoperative, due to an open Q24 transistor. According to the Boeing Commercial Airplane Group, the discrepancies discovered would result in the following: (1) If the left, outboard wheel started to skid, the wheel speed transducer signal would go to the left, inboard wheel skid detector circuit, which was inoperative. This would have allowed tire damage to occur to the left, outboard tire, since there would be no brake release. (2) If the left, outboard wheel locked up, the wheel speed transducer signal would go to the left, inboard wheel detector, providing a release of the left, inboard wheel, if the inboard locked wheel protection circuit was armed. Arming of the locked wheel protection circuit occurs when either the inboard wheel spin up to more than 30 mph, or the air/ground sensor switch is in the "air" position, to provide touchdown protection. (3) With the left inboard valve hydraulic lines crossed, sluggish braking would occur on the left, inboard wheel. The component examinations did not reveal evidence of malfunction of the right, main gear anti-skid or braking systems. The investigation was not able to determine if the crossed brake and return lines on the left, inboard anti-skid valve had any effect on right side braking. Boeing Commercial Airplane Group was asked to provide information to determine if the aircraft inspections performed by AAR Oklahoma, Inc. should have uncovered the discrepancies found in N4515W. Regarding the inoperative Q24 transistor, the ground test of the anti-skid system may have been affected by the crossed wheel speed transducer wiring. Without additional testing, it could not be determined if the inoperative Q24 transistor would have been discovered. Regarding the crossed wheel speed transducer wiring, the appropriate test for this was not referenced in the non-routine work cards, however that test is required if the landing gear is replaced. Regarding the crossed anti-skid valve brake and return lines, Boeing reported that this condition would result in sluggish braking on the left, inboard wheel.
ADDITIONAL INFORMATION
The tested aircraft system components were released to the operator, Air South. Inc. THE FLIGHT CREW REPORTED THAT THE FLIGHT PROCEEDED NORMALLY UNTIL THE LANDING ROLL. THE FIRST OFFICER FELT THE ANTISKID RELEASING, AND THE CAPTAIN TOOK OVER THE CONTROLS. BRAKING ACTION WAS INITIALLY FELT, THEN ALL BRAKING ACTION WAS LOST. THE AIRCRAFT DEPARTED THE END OF THE RUNWAY, AND CAME TO A STOP ABOUT 200 FEET PAST THE DEPARTURE END, IN THE GRASS. THE LEFT OUTBOARD MAIN TIRE WAS BLOWN. EXAMINATION OF THE AIRCRAFT REVEALED THAT THE LEFT, INBOARD ANTISKID VALVE BRAKE AND RETURN LINES WERE CROSSED. THE LEFT, INBOARD SKID DETECT CIRCUIT WAS FOUND INOPERATIVE. ALSO, THE WIRING TO THE LEFT, INBOARD AND LEFT, OUTBOARD WHEEL SPEED TRANSDUCERS WERE CROSSED. THERE WAS ALSO EVIDENCE THAT THE AIRCRAFT HAD HYDROPLANED NEAR THE DEPARTURE END OF THE RUNWAY. THE AIRCRAFT DISCREPANCIES WERE NOT DISCOVERED DURING ANTISKID SYSTEM TESTING PERFORMED ABOUT 2 WEEKS PRIOR TO THE ACCIDENT. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_ATL95IA043.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗