NTSB CAROL · Event
Event NYC99LA238
Registry · N100LK
FAA Aircraft Registry record.
Make / Model
BEECH F33A
Year of manufacture
1977 · 22 years old at event
Seats / Engines
5 seats · 1 engine
Last airworthiness date
19770317
ADS-B equipped
Yes — Mode-S A005B8
Registrant of record
KOEBELE THOMAS R
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's improper recover from a bounced landing. A factor related to the accident was the pilot's diverted attention due to the loss of a spouse.
Factual narrative
On September 24, 1999, about 1200 Eastern Daylight Time, a Beech F33A, N100LK, was substantially damaged while landing at the Cape May County Airport, Wildwood, New Jersey. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight conducted under 14 CFR Part 91. According to airport personnel, the airplane taxied to Runway 19, a 4,998 foot long asphalt runway, for departure. The airplane then departed unannounced, using the entire available runway, "barely" clearing the threshold lights located at the departure end of the runway. Airport personnel made repeated calls to the airplane on the UNICOM frequency to ask if there were any problems, but there were no replies. The airplane entered a "short pattern", returned to land, and touched down about mid-field on the runway. The airplane then began to bounce several times for the whole length of the runway before it gained a positive climb rate, and reentered the pattern. The airplane returned to land, and touched down about mid-field. It began to bounce several times again, before it struck the threshold lights, continued into an embankment, and sheared the nose gear off. The airplane came to rest upright in a grass field, about 460 feet from the departure end of the runway. A day after the accident, the pilot talked with airport personnel explaining that "he had lost his wife last week who he had been with since 1934." He additionally stated that "people make too many excuses today for their actions, and this accident was just plain and simply his fault." According to the pilot in a written statement, as the airplane touched down on the first landing, the engine would not throttle back. A go-around was initiated and the airplane was flown back to the runway for a planned "short landing." While landing for the second time, the pilot was able to throttle the engine back, "but insufficient to control [the] airplane to make a complete stop." The pilot had accumulated a total experience of about 16,000 flight hours. He had flown a total of 73 hours in the F33A, 6 hours of which were in the last 90 days. The owner of a repair facility in Hagerstown, Maryland, that worked on the airplane after the accident stated that the throttle lever connected to the throttle body was restricted in movement by a piece of the fuselage pushed near it during the accident. The fuselage was pulled away from the throttle lever and tagged with an Aircraft Condition Notice. A FAA Inspector examined the airplane in November 1999. He checked the throttle cable and the fuel injector throttle arm for freedom of movement throughout the operating range. No discrepancies were noted. Inspection of the wreckage in Hagerstown on December 7, 1999, by a Safety Board Investigator, revealed that the throttle moved freely with no noticeable friction. The airplane departed using the entire runway and returned to land. The airplane touched down about mid-field on the runway, then began to bounce several times for the whole length of the runway before gaining a positive climb rate. The airplane continued around the pattern for a second approach, touched down again about mid-field, and began to bounce several times, before it continued off the end of the runway. A day after the accident the pilot explained that 'he had lost his wife last week who he had been with since 1934.' He additionally stated that 'people make too many excuses today for their actions, and this accident was just plain and simply his fault.' The pilot had accumulated a total experience of about 16,000 flight hours. He had flown a total of 73 hours in the F33A, 6 hours of which were in the last 90 days. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_NYC99LA238.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 (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.
- 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…
Browse the full corpus — academia portal ↗