Skip to content

Public Record · As of May 5, 2026

N260DB

Babcock Dayton STALKER · 2010 View Type →

Status

Registration Valid

Type

Weight-Shift-Control

Engine

ROTAX 503 DCDI

Last Cert Issue

—

Aircraft Resources

Engine · Rotax Aircraft Engines → Search FAA TCDS for BABCOCK DAYTON STALKER →

01 /  Registration

Filed with the Federal Aviation Administration

Every cell below is a literal field from the FAA Aircraft Registry. Click any value to open the FAA registry record for N260DB.

Tail Number

N260DB

Serial Number

DBS01

Make

BABCOCK DAYTON

Model

STALKER

Year of Manufacture

2010

Mfr / Model Code

05629SB

Type Aircraft

Weight-Shift-Control

Type Engine

2-Cycle

Engines

1

Seats

2

Engine Manufacturer

ROTAX

Engine Model

503 DCDI

Horsepower

52 hp

Weight Class

CLASS 1

Certification

Experimental (+1 flag) · code 42

Registrant

KLEBENOW JEFFERY J · Individual

Address

6594 N CHOLLA LN · CASA GRANDE, AZ 85194-6896

FAA Region

4 · County 021

Status

Registration Valid

Airworthiness Date

—

Cert Issue Date

—

Expiration Date

—

Last FAA Action

—

Mode S Hex (ICAO24)

A27F4A

Mode S (Octal)

50477512

Live position via ICAO24 A27F4A

ADS-B Exchange → FlightAware → FlightRadar24 →

External services. Live tracks are unaffiliated with TallyAero or the FAA.

02 /  NTSB Records

Events on file with the National Transportation Safety Board

03 /  Airworthiness Directives

Applicable to BABCOCK DAYTON STALKER

Federal Aviation Administration airworthiness directives matched to make and model. Each entry links to the Federal Register publication.

No matching airworthiness directives are on file for this make and model in the Federal Register.

04 /  Service Difficulty Reports

FAA SDR filings

The FAA does not currently expose a public API for Service Difficulty Reports. We do not back-fill or paraphrase. Search the FAA SDR portal directly →

05 /  Sources & Methodology

Every fact on this page links to its primary US-government source

We render only what the agency publishes. Found a factual error? Report it → We acknowledge within 5 business days and resolve within 14.