NTSB CAROL · Event
Event SEA98LA144
Registry · N53630
FAA Aircraft Registry record.
Make / Model
CESSNA 172P
Year of manufacture
1981 · 17 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19810317
ADS-B equipped
Yes — Mode-S A6C991
Registrant of record
ARLINGTON FLIGHT SERVICES INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_SEA98LA144.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 (loss of control). 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 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
- NASA NTRS 2021 · Conference Paper
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
Browse the full corpus — academia portal ↗