WELL · 42-143-30975 · DISTRICT 7

Gibson #1

Plugged

Erath County · John R. Jacobs (Bend Congl.) field  · Vertical

Gibson #1 (API 42-143-30975) is a plugged well in Erath County, plugged February 11, 2017, last operated by Reval Exploration LLC.

The RRC has issued one drilling permit (amended once), issued February 21, 1997, permitted to 3,900 ft.

It was permitted by Sabre Oil And Gas Corp. and has since transferred to Reval Exploration LLC on the wellbore schedule.

Completion filings report one formation top, including Big Saline.

Operator of record

Reval Exploration LLC

Permitted by Sabre Oil and Gas Corp.; the EWA schedule now lists a different operator.

Phoenix, AZ · P-5 Y, filed Jul 7, 2017 · (817) 454-3094

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleReval Exploration LLC
Production reportsRazor Resources, Inc.through Jun 2009
Latest permitSabre Oil and Gas Corp.Feb 21, 1997

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

3,900
total depth, ft
2
permits on file
Feb 21, 1997
last permit issued
Apr 17, 1997
completed
0
cumulative oil, bbl
1.14M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 1997 THROUGH Feb 2017

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 17, 1997
Shut in
—
Plugged
Feb 11, 2017

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
Gibson G-8-163006John R. Jacobs (Bend Congl.)Reval Exploration LLC101.03MApr 1997 – Feb 2017
Gibson G-8-163110Big Wally (Basal Congl.)Reval Exploration LLC10109KApr 1997 – Feb 2017

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. 1Sabre Oil and Gas Corp.Apr 1997 → Jan 2008
  2. 2Razor Resources, Inc.Feb 2008 → Jun 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
458934-98DrillSabre Oil and Gas Corp.May 6, 1997Feb 21, 1997Mar 27, 19973,900
458934-99DrillSabre Oil and Gas Corp.Feb 21, 1997Feb 21, 1997—3,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-163006————
—— G-8-163110————

Formation tops

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

FormationMD ftSubsea
Big Saline3,026-2,022

Perforations

Perforated and open-hole intervals.

FromToType
3,1113,119Perforated
3,1933,201Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62520612.25140 S
5.53,2707.875300 S
5.5—7.875300 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 11, 1997May 2, 1997Yes
00Jul 3, 1997May 2, 1997Yes
00Jun 12, 1997—Yes
00Jun 6, 1997—Yes

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