WELL · 42-417-36994 · DISTRICT 7

Timely East #1

N

Shackelford County · Shackelford County Regular (Gas) field  · Vertical

Timely East #1 (API 42-417-36994) is a well in Shackelford County operated by Dragon Land & Cattle CO. Inc., completed October 5, 1989.

The RRC has issued one drilling permit (amended once), issued December 31, 1986, permitted to 5,450 ft.

It was permitted by Knightsbridge Petroleum Corp. and has since transferred to Dragon Land & Cattle CO. Inc. on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Dragon Land & Cattle Co. Inc.

Permitted by Knightsbridge Petroleum Corp.; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 6, 1996 · 4 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDragon Land & Cattle Co. Inc.
Production reportsnone
Latest permitKnightsbridge Petroleum Corp.Dec 31, 1986

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

5,450
total depth, ft
2
permits on file
Dec 31, 1986
last permit issued
Oct 5, 1989
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 5, 1989
Shut in
—
Plugged
—

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Brewster O-8-26364Shackelford County RegularSequoia Natural Gas, Inc.300Jan 1993 – Jul 2026
— G-8-132951——000—

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
324599-98DrillKnightsbridge Petroleum Corp.Feb 24, 1987Dec 31, 1986—4,500
324599-99DrillKnightsbridge Petroleum Corp.Dec 19, 1986Dec 31, 1986—5,450

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-132951————
—— O-8-26364————

Perforations

Perforated and open-hole intervals.

FromToType
3,8403,856Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252101190 S
4.51,0807.875160 S
4.54,2177.875175 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 15, 2002Dec 3, 2001—
00Apr 14, 1992Oct 28, 1991—
00Mar 20, 1992——
00Jan 22, 1990Jan 12, 1990Yes
00Jan 17, 1990——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
114K
bbl, all reported
Jul 2016
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000076484H-1 InjectionCanceled Nov 21, 20223008003,840–3,856

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120152016

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/41736994, documented in the API reference.