WELL · 42-363-34102 · DISTRICT 7

Gragg #1

Plugged

Palo Pinto County · Palo Pinto County Regular field  · Vertical

Gragg #1 (API 42-363-34102) is a plugged well in Palo Pinto County, plugged July 15, 2019, last operated by Jeff Dooley Operating LLC.

The RRC has issued one drilling permit, issued September 5, 1991, permitted to 4,999 ft.

It was permitted by Three P Operating Company and has since transferred to Jeff Dooley Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Caddo, Marble Falls, Mississippian.

Its lease has reported 14.6K barrels of oil and 28.6K mcf of gas since January 1993, last reporting in March 2020. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Jeff Dooley Operating LLC

Permitted by Three P Operating Company; the EWA schedule now lists a different operator.

Breckenridge, TX · P-5 Y, filed Jan 5, 2026 · 2 permits on file · (254) 559-0990

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJeff Dooley Operating LLC
Production reportsThree P Operating Companythrough Nov 2006
Latest permitThree P Operating CompanySep 5, 1991

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

4,999
total depth, ft
1
permits on file
Sep 5, 1991
last permit issued
Jan 2, 1992
completed
14.6K
cumulative oil, bbl
28.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 2, 1992
Shut in
—
Plugged
Jul 15, 2019

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gragg O-8-26402Palo Pinto County RegularJeff Dooley Operating, LLC214.6K28.6KJan 1993 – Mar 2020

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. 1Three P Operating CompanyJan 1993 → Nov 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
391512-99DrillThree P Operating CompanySep 3, 1991Sep 5, 1991Sep 27, 19914,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-26402————

Formation tops

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

FormationMD ftSubsea
Caddo3,604-2,474
Marble Falls4,200-3,070
MississippianMISSISSIPPI4,396-3,266

Perforations

Perforated and open-hole intervals.

FromToType
2,9973,006Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62513812.2585 S
4.53,2707.875150 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
00Feb 28, 1992Jan 8, 1992Yes
00Jan 14, 1992——

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