WELL · 42-083-36205 · DISTRICT 7

J.P. Jones & Fern Jones Trust #3

Y

Coleman County · Coleman County Regular field · Shut IN  · Vertical

J.P. Jones & Fern Jones Trust #3 (API 42-083-36205) is a well in Coleman County operated by Flint Rock Resources Mgmnt Inc., completed July 23, 2017 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued May 2, 2017, permitted to 2,500 ft.

Completion filings report 10 formation tops, including Capps Lime - Disposal, Breneke Sand - Disposal, Canyon, Coleman Junction.

Its lease has reported 10.5K barrels of oil since May 2017, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Flint Rock Resources Mgmnt Inc.

Austin, TX · P-5 Y, filed May 4, 2026 · 45 permits on file · (512) 801-1622

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFlint Rock Resources Mgmnt Inc.
Production reportsFlint Rock Resources Mgmnt, Inc.through Feb 2026
Latest permitFlint Rock Resources Mgmnt, Inc.May 2, 2017
2,500
total depth, ft
1
permits on file
May 2, 2017
last permit issued
Jul 23, 2017
completed
10.5K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 23, 2017
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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
J.P. Jones & Fern Jones Trust O-8-32157Coleman County RegularFlint Rock Resources Mgmnt, Inc.310.5K0May 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 454 · prior 12 537(-15%)

050100202420252026

Chain of custody

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

  1. 1Flint Rock Resources Mgmnt, Inc.May 2017 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
825996-99DrillFlint Rock Resources Mgmnt, Inc.Apr 27, 2017May 2, 2017May 31, 20172,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-32157————

Formation tops

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

FormationMD ftSubsea
Capps Lime - Disposal2,249-515
Breneke Sand - Disposal——
CanyonCANYON REEF - DISPOSAL——
Coleman Junction——
Cook Sand - Disposal——
Crosscut Upper - Disposal——
King Sand - Disposal——
Overall - Disposal——
TannehillTANNEHILL - DISPOSAL——
Winchell Lime - Disposal——

Perforations

Perforated and open-hole intervals.

FromToType
2,0922,110Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62512612.2590 S
5.52,2907.875320 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 19, 2019Nov 28, 2018Yes

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