SEA02LA050
2002-03-05 · West Jordan, Utah, United States · None · 1 aircraft · Status: Completed
Airport U42
Current FAA registration · N278GJ
- Make / Model
- UNANDER GARY D VELOCITY 173 RG
- Seats / Engines
- 4 seats · 1 engine
- ADS-B equipped
- Yes — Mode-S A2C4D3
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to ensure that the gear was extended prior to landing. Factors included a failure of a hydraulic down-pressure switch, and the pilot's attention diverted to another aircraft executing an opposite-direction traffic pattern.
Factual narrative
On March 5, 2002, approximately 1855 mountain standard time, an Unander Velocity 173RG experimental-category amateur-built airplane, N278GJ, was substantially damaged in a gear-up landing at Salt Lake City Municipal Airport #2 (Salt Lake #2), West Jordan, Utah. The private pilot-in-command and one passenger were not injured in the accident. Visual meteorological conditions were reported at Salt Lake #2 at 1855, and no flight plan was filed for the 14 CFR 91 personal flight from Wendover, Utah. The pilot reported that he was attempting a landing after dark on runway 16 at the non-towered airport. The accident pilot reported that as he was turning base for runway 16, another aircraft (registration number not reported or determined), which he had passed on the way into Salt Lake #2, announced that he was entering downwind for runway 34. The pilot reported that he attempted to talk to the pilot of the other aircraft on the radio, but got no response (NOTE: According to the U.S. Government Airport/Facility Directory (A/FD), Salt Lake #2's Common Traffic Advisory Frequency [CTAF] frequency is 122.7 MHz.) The pilot stated that he put the gear switch down, but forgot to check for three green lights since his attention was diverted to the other aircraft. The pilot stated that he saw the other aircraft turning final as he (the accident pilot) was about to flare. The pilot reported that he then attempted to initiate a go-around, but the aircraft's propeller struck the runway and the engine stopped. The aircraft touched down on the sod on the side of the runway and subsequently struck an object on the ground and slid partially back onto the runway. The pilot stated that the other aircraft subsequently landed on runway 34 and went past the accident aircraft. An FAA inspector who was at the airport at the time reported that the landing gear handle was in the "down" position at the accident scene, but that the gear appeared to have never come out of the wells. The pilot of the other aircraft was not identified to the NTSB and was not contacted. The pilot reported that a hydraulic down pressure switch (part number 0166-41604-3-064) had failed, disabling normal landing gear extension. The pilot reported the total time on the part as 3 hours, and stated that he had just replaced this switch after a previous switch had failed. The pilot indicated in his NTSB accident report that the aircraft kit maker, Velocity Aircraft of Sebastian, Florida, had been made aware of this problem. Salt Lake #2 is equipped with an AWOS-3 automated weather observation system (AWOS) that broadcasts automated weather observations on 134.425 MHz. Winds at the airport were reported as being calm at 1755, then from 240 degrees true at 8 knots at 1855 and from 250 degrees true at 7 knots at 1955. The A/FD does not specify a calm-wind or preferred runway for the airport. The pilot reported that he was attempting a landing after dark on runway 16 at the non-towered airport. The accident pilot reported that as he was turning base for runway 16, another aircraft (registration number not reported or determined), which he had passed on the way into Salt Lake #2 Airport, announced that he was entering downwind for runway 34. The pilot reported that he attempted to talk to the pilot of the other aircraft on the radio, but got no response. The pilot stated that he put the gear switch down, but forgot to check for three green lights since his attention was diverted to the other aircraft. The pilot stated that he saw the other aircraft turning final as he (the accident pilot) was about to flare. The pilot reported that he then attempted to initiate a go-around, but the aircraft's propeller struck the runway and the engine stopped. The aircraft touched down on the sod on the side of the runway and subsequently struck an object on the ground and slid partially back onto the runway. The pilot stated that the other aircraft subsequently landed on runway 34 and went past the accident aircraft. An FAA inspector who was at the airport at the time reported that the landing gear handle was in the "down" position at the accident scene, but that the gear appeared to have never come out of the wells. The pilot of the other aircraft was not identified to the NTSB, and was not contacted. The pilot reported that a hydraulic down pressure switch had failed, disabling normal landing gear extension. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2002_SEA02LA050.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…