WELL · 42-215-30973 · DISTRICT 4

C & K Petroleum Corp. Fee #1

Plugged

Hidalgo County · Mercedes (8920) field  · Vertical

C & K Petroleum Corp. Fee #1 (API 42-215-30973) is a plugged well in Hidalgo County, plugged March 19, 2004, last operated by Texoil Production Inc..

The RRC has issued 3 drilling permits between 1979 and 1989, permitted to 9,500 ft.

It was permitted by Texas Independent Explor., Inc. and has since transferred to Texoil Production Inc. on the wellbore schedule.

Operator of record

Texoil Production Inc.

Permitted by Texas Independent Explor., Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jan 5, 1993 · 8 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTexoil Production Inc.
Production reportsnone
Latest permitTexas Independent Explor., Inc.Mar 16, 1989

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

9,500
total depth, ft
3
permits on file
Mar 16, 1989
last permit issued
Feb 21, 1981
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2004

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 21, 1981
Shut in
—
Plugged
Mar 19, 2004

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
Smith Gas Unit #1 G-4-130166Mercedes ( 3-N-1)Texas Independent Explor Ltd.100Jan 1993 – Mar 2004

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
356758-99RecompletionTexas Independent Explor., Inc.Mar 7, 1989Mar 16, 1989—9,000
116172-99OtherCox, Edwin L. & Cox, Berry R.Apr 27, 1981Apr 27, 1981—9,500
61433-99DrillCox, Edwin L.Oct 22, 1979Oct 22, 1979Oct 27, 19799,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-130166————

Perforations

Perforated and open-hole intervals.

FromToType
8,1828,190Perforated
8,1848,190Perforated
8,9258,932Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,72910.75695 S
8.6251,72912.25695 S
2.3758,743——
2.3758,807——
4.59,1327.875600 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
00May 22, 1989Mar 10, 1989Yes
00Apr 1, 1989——
00Jan 12, 1984Apr 1, 1981—
00Jan 12, 1984Jun 20, 1980—

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
0
bbl, all reported
Jan 2004
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000072648W-14 DisposalPlugged Apr 5, 20042001,0507,080–7,090

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

Last 12 months 0 · prior 12 0

0120032004

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