WELL · 42-165-01209 · DISTRICT 8

Jones John S. #2

Plugged

Gaines County · Hobbs East (4400) field  · Vertical

Jones John S. #2 (API 42-165-01209) is a plugged well in Gaines County, plugged May 23, 2018, last operated by Fortuna Resources Dvlpment LLC.

The RRC has issued 2 drilling permits between 1984 and 1994, permitted to 5,975 ft.

It was permitted by Exxon Corp. and has since transferred to Fortuna Resources Dvlpment LLC on the wellbore schedule.

Completion filings report 2 formation tops, including San Andres, Glorieta.

Operator of record

Fortuna Resources Dvlpment LLC

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

Houston, TX · P-5 Y, filed Jan 4, 2026 · 28 permits on file · (281) 404-4490

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFortuna Resources Dvlpment LLC
Production reportsExxon Corp.through May 1994
Latest permitExxon Corp.Mar 22, 1994

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

5,975
total depth, ft
2
permits on file
Mar 22, 1994
last permit issued
Dec 22, 1984
completed
0
cumulative oil, bbl
13
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 22, 1984
Shut in
—
Plugged
May 23, 2018

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Jones, John S. O-11-65265Hobbs, East (4400)Fortuna Resources Dvlpment, LLC100Jan 1993 – Jul 2018
Jones, John S. G-11-150143Hobbs, East (Queen Gas)Fortuna Resources Dvlpment, LLC1013May 1994 – May 2018

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. 1Exxon Corp.May 1994 → May 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
420385-99RecompletionExxon Corp.Jan 19, 1994Mar 22, 1994May 11, 19945,975
252457-99OtherExxon Corp.Dec 27, 1984Sep 24, 1984—5,830

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-11-150143————
—— O-11-65265————

Formation tops

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

FormationMD ftSubsea
San Andres4,448-863
Glorieta5,816-2,231

Perforations

Perforated and open-hole intervals.

FromToType
3,6993,960Perforated
4,4684,486Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,917——
10.751,918——
7.6254,017——
7.6254,106——

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
00Aug 29, 1994Jul 12, 1994Yes
00Jul 28, 1994——
00Apr 1, 1985Jan 16, 1985—
00Mar 29, 1985——

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) and the University Lands library. 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/16501209, documented in the API reference.