# NTSB SEA98LA144: Cessna 172P, N53630, Seattle, WA, July 19, 1998 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 18, 1998, 20:30 local (Jul 19, 1998, 03:30 UTC) - Place: Seattle, WA - Coordinates: 47.540912, -122.309165 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.5409&lon=-122.3092&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report February 15, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 43575 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA98LA144 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/43575/pdf - Page: https://openairdocs.org/ntsb/SEA98LA144 ## Probable cause The student pilot's failure to maintain directional control of the aircraft. Related factors were the student pilot's lack of total experience, and airport signs in the accident area. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - directional control - not maintained, pilot in command (cause) - lack of total experience, pilot in command (contributing factor) - On ground/water collision with object, landing - object - airport sign/marker (contributing factor) ## Analysis The accident occurred on the second landing attempt during the student pilot's first solo flight. The pilot reported that on touchdown, the airplane appeared left of centerline so he applied right rudder. The airplane was observed to touch down right wheel first, left of the runway centerline. The pilot reported he then neutralized the rudder, but that the airplane was going toward the side of the runway at that time. The airplane departed the right side of the runway, where it struck airport signs. The student pilot had 25.3 hours total time. The student pilot's flight instructor reported no mechanical failure or malfunction was involved. ## Factual narrative On July 18, 1998, approximately 2030 Pacific daylight time, a Cessna 172P, N53630, operated by Wings Aloft Inc. of Boeing Field/King County International Airport, Seattle, Washington, was substantially damaged in a loss of control occurrence during a touch-and-go landing attempt on Boeing Field runway 13L. Following the loss of control, the aircraft departed the surface of runway 13L and struck and damaged airport signs. The student pilot, who was on his first solo flight, was not injured in the accident. Visual meteorological conditions prevailed and no flight plan had been filed for the 14 CFR 91 local instructional flight out of Boeing Field. Preliminary information furnished to the NTSB by the airport police, who conducted the initial response to the accident scene, indicated that the student pilot lost control of the aircraft shortly after touchdown, at a point approximately 150 feet north of the A-4 taxiway (NOTE: the A-4 taxiway intersects runway 13L approximately 1,600 feet southeast of the runway threshold.) The aircraft left the pavement, continuing in a southwesterly direction for approximately 125 feet across a grass island. It then entered the section of taxiway A-4 between runways 13L and 13R, striking and shearing off a combination ILS HOLD/runway designator sign located on the north side of that taxiway. The aircraft then continued southwest across the A-4 taxiway and traveled approximately 125 feet before coming to rest on an easterly heading approximately 90 feet west of runway 13L. Winds were reported as being from 180 degrees at 8 knots in Boeing Field's 2045 hourly observation. In a written statement to Wings Aloft, which Wings Aloft furnished to the NTSB with its operator's report of accident, the student pilot, a native of India, reported: On touchdown, the aircraft appeared to be on the left of the center line. Right rudder was applied to correct for that. The aircraft got dragged [a] little more [and] went on one wheel, the right wheel. I let it [sic] go the rudder to neutral so that the aircraft would come back to its neutral position on three wheels. However, since it was already drifted, it was going towards the side of the runway [and] hit the runway signboard [and] got deflected in the grass on the right of the runway. The student pilot's flight instructor, who was observing the pilot from the Boeing Field flight line at the time, reported that after 4 dual touch-and-go landings immediately prior to the accident, the student dropped her off at the airport terminal. She stated that his first landing was "slightly bumpy, but fine overall." She reported that on final approach for the second landing, "the airplane appeared to be slightly high, resulting in a landing farther down the runway than usual." She stated that the airplane touched down right wheel first, slightly left of centerline, and that she was unable to see whether the left wheel ever touched down. She reported the airplane "then careened right, lifting slightly onto the right wheel, stabilized heading toward the taxiway, hit two signs, and went into the grass while being turned left 90 degrees." The flight instructor, who prepared the operator's report of accident, reported that no mechanical failure or malfunction was involved in the accident. She reported the student pilot's total time as 25.3 hours. Boeing Field runway 13L is a 3,710 foot long by 100 foot wide asphalt surface runway. The runway threshold is displaced 240 feet, giving a usable landing distance of 3,470 feet. The runway is equipped with a 2-bar visual approach slope indicator (VASI) on the left side of the runway. The VASI is set for a glide path angle of 3.34 degrees and a threshold crossing height of 49 feet. ## Aircraft - Registration: [N53630](https://openairdocs.org/aircraft/N53630), registered now, S/N 17274789, built 1981 (OpenAirDocs) - Reported make and model: Cessna 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17274789 - Engines: Lycoming O-320-D2J 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Wings Aloft Inc. - Registered owner: Wilbur F. Van Pelt - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: AAIP, March 6, 1998 - Departed: BFI - Airport: BFI, Boeing Fld/King Co Intl, runway 13L, 3,470 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 25; student; medical: class 1, valid medical--w/ waivers/lim; seat: left; flight hours: 26 total, 26 in this make and model, 26 in the last 90 days, 14 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 8 knots - Visibility: 30 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 57 °F - Altimeter: 29.00 inHg - Observed at: BFI ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19980718023969A](https://openairdocs.org/incident/19980718023969A), Jul 18, 1998: Cessna 172P, Seattle, WA, Substantial damage. First solo lost control landing in crosswind. Exited runway. Struck runway signs. Added power then aborted. (.4)the accident occurred on the second landing… 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. --- 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.