WELL · 42-355-33239 · DISTRICT 4

King Richard #1

Y

Nueces County · Richard King (Frio Cons.) field · Producing  · Vertical

King Richard #1 (API 42-355-33239) is a well in Nueces County operated by Durango Resources Corp., completed September 6, 2000 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 18, 2000, permitted to 6,500 ft.

It was permitted by Synergy Oil & Gas, Inc. (A) and has since transferred to Durango Resources Corp. on the wellbore schedule.

Completion filings report 2 formation tops, including Frio, Vicksburg.

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

Operator of record

Durango Resources Corp.

Permitted by Synergy Oil & Gas, Inc. (A); the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Feb 4, 2026 · 18 permits on file · (713) 253-4685

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDurango Resources Corp.
Production reportsDurango Resources Corp.through Feb 2026
Latest permitSynergy Oil & Gas, Inc. (A)Jul 18, 2000

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

6,500
total depth, ft
1
permits on file
Jul 18, 2000
last permit issued
Sep 6, 2000
completed
0
cumulative oil, bbl
421K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 6, 2000
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
King, Richard G-4-179283Richard King (Frio Cons.)Durango Resources Corp.10421KSep 2000 – Jul 2026

Gas, mcf lease total

Last 12 months 826 · prior 12 290(+185%)

0100200202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Synergy Oil & Gas, Inc. (A)Sep 2000 → Aug 2001
  2. 2Penn Virginia Oil & Gas Corp.Sep 2001 → Mar 2002
  3. 3Durango Resources Corp.Apr 2002 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
497343-99DrillSynergy Oil & Gas, Inc. (A)Jul 18, 2000Jul 18, 2000Aug 14, 20006,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-179283————

Formation tops

As filed on W-2/G-1. Subsea from 11 ft elevation.Download CSV →

FormationMD ftSubsea
Frio4,020-4,009
Vicksburg5,800-5,789

Perforations

Perforated and open-hole intervals.

FromToType
5,4645,572Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62597512.25435 S
5.56,5007.875695 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
00Dec 16, 2000Oct 13, 2000Yes
00Nov 7, 2000——

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.

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/35533239, documented in the API reference.