WELL · 42-355-30229 · DISTRICT 4

Knight, R. R. #1

N

Nueces County  · Vertical

Knight, R. R. #1 (API 42-355-30229) is a permitted well in Nueces County filed by Continental Trend Resources, Inc; no completion report is on file yet.

The RRC has issued 4 drilling permits between 1980 and 2003, permitted to 11,500 ft.

Completion filings report one formation top, including Frio.

Operator of record

Continental Trend Resources, Inc

Oklahoma City, OK · P-5 Y, filed Nov 4, 2022 · 164 permits on file · (405) 234-9000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsContinental Trend Resources, Incthrough Oct 2003
Latest permitContinental Trend Resources, IncSep 12, 2003
11,500
total depth, ft
4
permits on file
Sep 12, 2003
last permit issued
—
completed
0
cumulative oil, bbl
22.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2004

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Knight, R.R. G-4-140602Petronilla (10,950)Continental Trend Resources, Inc1022.3KJan 1993 – Sep 2004
— O-4-10024——000—

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

Chain of custody

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

  1. 1Kamlok Oil & Gas, Inc.Jan 1993 → Dec 1995
  2. 2S N D Energy Company, Inc.Jan 1996 → Mar 2000
  3. 3Continental Trend Resources, IncSep 2000 → Oct 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
535595-99RecompletionContinental Trend Resources, IncAug 20, 2003Sep 12, 2003—11,500
374144-99RecompletionKamlok, Inc.Jun 6, 1990Jun 7, 1990—11,500
136516-99RecompletionAmoco Production CompanyOct 2, 1981Oct 2, 1981—11,500
72119-99RecompletionAmoco Production CompanyFeb 4, 1980Feb 4, 1980—11,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-140602————
—— O-4-10024————

Formation tops

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

FormationMD ftSubsea
FrioFRIO 74757,479-7,430
FrioFRIO 75507,570-7,521
FrioFRIO 76707,640-7,591
FrioFRIO 97609,761-9,712
FrioFRIO 1120011,200-11,151
FrioFRIO 1130011,318-11,269

Perforations

Perforated and open-hole intervals.

FromToType
9,7619,785Perforated
10,94510,967Perforated
11,22011,240Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
206826100 S
13.6251,30217.51,000 S
13.3751,30217.51,000 S
9.6258,55012.25650 S
5.511,4888.8751,025 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
00Mar 6, 1992Jan 24, 1992—
00Feb 20, 1992——
00Jan 12, 1984Jan 22, 1982—
00Jan 12, 1984Jun 23, 1980—
00Jan 12, 1984Dec 20, 1973—
00Jan 12, 1984——

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