WELL · 42-261-31373 · DISTRICT 4

Kenedy John G. Jr. J #41

Y

Kenedy County · EL Paistle Deep (Frio) field · Producing  · Vertical

Kenedy John G. JR. J #41 (API 42-261-31373) is a well in Kenedy County operated by Headington Energy Partners LLC, completed August 12, 2005 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 7, 2004, permitted to 19,000 ft.

It was permitted by Headington Oil Company, L.P. and has since transferred to Headington Energy Partners LLC on the wellbore schedule.

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

Operator of record

Headington Energy Partners LLC

Permitted by Headington Oil Company, L.P.; the EWA schedule now lists a different operator.

Corpus Christ, TX · P-5 Y, filed Jun 4, 2026 · 175 permits on file · (361) 885-0110

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHeadington Energy Partners LLC
Production reportsHeadington Energy Partners, LLCthrough Apr 2026
Latest permitHeadington Oil Company, L.P.Sep 7, 2004

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

19,000
total depth, ft
1
permits on file
Sep 7, 2004
last permit issued
Aug 12, 2005
completed
0
cumulative oil, bbl
4.41M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 12, 2005
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
Kenedy, John G. Jr. "J" G-4-213100EL Paistle, Deep (Frio)Headington Energy Partners, LLC104.41MFeb 2005 – Jul 2026

Gas, mcf lease total

Last 12 months 5,736 · prior 12 6,622(-13%)

05001K202420252026

Chain of custody

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

  1. 1Headington Oil Company, L.P.Apr 2005 → Mar 2008
  2. 2Headington Oil Company LLCApr 2008 → Oct 2014
  3. 3Exxon Mobil CorporationMar 2009 → Jun 2012
  4. 4Headington Energy Partners, LLCApr 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
550550-99DrillHeadington Oil Company, L.P.Sep 7, 2004Sep 7, 2004Sep 25, 200419,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-213100————

Perforations

Perforated and open-hole intervals.

FromToType
15,45116,426Perforated
16,69017,666Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,51717.51,500 S
9.62513,19812.251,200 S
516,0917.625350 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
00Jul 24, 2007Jul 17, 2007—
00Apr 3, 2006Jun 2, 2005Yes
00Jan 9, 2006——

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