NTSB CAROL · Event
Event CEN13IA177
Registry · N613TX
FAA Aircraft Registry record.
Make / Model
LANCAIR LANCAIR EVOLUTION
Year of manufacture
2012 · 1 years old at event
Engine
P&W CANADA PT6A-135 (750 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20120612
ADS-B equipped
Yes — Mode-S A7FBA2
Registrant of record
LIFSEY WALTER T
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilots' failure to verify landing gear extension before landing.
Factual narrative
On February 21, 2013, about 0930 eastern standard time, a TTX Lancair Evolution airplane, N613TX, sustained minor damage during a gear-up landing at the Eagle Creek Airpark (EYE), Indianapolis, Indiana. The pilot and flight instructor were not injured. The airplane was registered to and operated by TTX Air, LLC, under the provisions of 14 Code of Federal Regulations Part 91 as an instructional flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The local flight originated from EYE about 0910.The pilot reported that they were conducting takeoffs and landings in the airport traffic pattern when the incident occurred. He noted that the first two landings were uneventful. He stated that after the third takeoff, the landing gear position indicator lights remained green (indicating gear down) after the selector handle was moved to the retracted position. The selector handle was cycled and the landing gear appeared to retract normally at that time. The next landing and takeoff were routine. The pilot stated that on the next landing, he intended to execute a no-flap (flaps up) full stop landing. He stated that the landing gear selector handle was lowered on the downwind traffic pattern leg, abeam the end of the runway. The pilot noted that becoming fixated on the requirements of the no-flap landing likely precluded his confirmation of the landing gear position; three green indicator lights. He recalled hearing the landing gear warning tone as the airplane entered the landing flare with the engine power at idle. This was shortly before the airplane contacted the runway with the landing gear retracted. In his report, the pilot noted a breakdown in crew resource management and checklist usage. The flight instructor reported that the pilot selected landing gear down abeam the landing point on the runway while on the downwind leg of the traffic pattern. He noted that they were focused on maintaining the proper airspeed and approach angle. He did not recall verifying the landing gear position indication. As the airspeed decreased below 95 knots on final approach, he became aware of the landing gear warning tone. However, the airplane began to contact the runway before he could initiate a go-around. The airplane came to rest with the landing gear retracted in the grass area, about 30 feet east of runway 3. The airplane traveled about 1,844 feet from the initial touchdown point to the final resting point. Two runway lights were damaged during the runway excursion. A postincident examination of the landing gear extension/retraction system did not reveal any anomalies. The extension/retraction cycles were initiated with the cockpit landing gear selector switch. The landing gear position indicator lights operated normally during the examination. The landing gear aural warning system activated at a simulated airspeed of 100 knots. The pilot and flight instructor were conducting takeoffs and landings in the airport traffic pattern when the incident occurred. The pilot stated that, during the incident landing, he lowered the landing gear selector handle while on the downwind traffic pattern leg, abeam the runway end. The pilot stated that he intended to execute a no-flap, full-stop landing and that, because he was concentrating on the no-flap landing, he might not have properly verified the landing gear position before landing. The pilots recalled hearing the landing gear aural warning as the airplane entered the landing flare with the engine power at idle. The airplane contacted the runway before a go-around could be initiated. The landing gear extension/retraction system and the landing gear position indicator lights operated normally during a postincident examination. During the examination, the landing gear aural warning system activated at a simulated airspeed of 100 knots. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Action/decision-Action-Forgotten action/omission-Flight crew - C
- C Personnel issues-Task performance-Use of equip/info-Use of checklist-Flight crew - C
Verbatim from NTSB's published report. Source file
NTSB_2013_CEN13IA177.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 (runway excursion, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- 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.
Browse the full corpus — academia portal ↗