TEXAS · WELLS · PANOLA COUNTY · SABINE ROYALTY LEASE · API 42-365-31385 · DISTRICT 06

Sabine Royalty #3

Plugged

Panola County · Belle Bower (Pettit Lo.) field  · Vertical

Sabine Royalty #3 (API 42-365-31385) is a plugged well in Panola County, plugged November 3, 2017, last operated by Petroquest Energy L.L.C..

The RRC has issued one drilling permit, issued November 17, 1981, permitted to 7,000 ft.

It was permitted by Marshall Expl. Inc. and has since transferred to Petroquest Energy L.L.C. on the wellbore schedule.

Its lease has reported 20.9K barrels of oil and 302K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Petroquest Energy L.L.C.

Permitted by Marshall Expl. Inc.; the EWA schedule now lists a different operator.

Based in
Lafayette, LA
P-5 status
Delinquent (D)
P-5 last filed
Feb 20, 2025
Permits on file
113
Phone
(337) 232-7028

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetroquest Energy L.L.C.
Production reportsPetroquest Energy, L.L.C.through Jul 2014
Latest permitMarshall Expl. Inc.Nov 17, 1981

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

7,000
total depth, ft
1
permits on file
Nov 17, 1981
last permit issued
Jan 27, 1982
completed
20.9K
cumulative oil, bbl
302K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 27, 1982
Shut in
—
Plugged
Nov 3, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sabine Royalty O-6-10640Belle Bower (Pettit, Lo.)Petroquest Energy, L.L.C.120.9K302KJan 1993 – Jul 2026

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. 1Apache CorporationJan 1993 → Nov 1997
  2. 2Bristol Resources CorporationDec 1997 → Jul 2000
  3. 3Chaparral (USA) Energy, Inc.Oct 2000 → Sep 2002
  4. 4Chaparral Energy, L.L.C.Oct 2002 → May 2013
  5. 5Petroquest Energy, L.L.C.Jun 2013 → Jul 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
140917-99DrillMarshall Expl. Inc.Nov 17, 1981Nov 17, 1981Nov 23, 19817,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 27, 1982Sabine Royalty O-6-10640Belle Bower (Pettit Lo.)Petroquest Energy L.L.C.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
6,2346,239Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,02312.25500 S
2.3756,207——
5.57,0007.875850 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
00Jan 12, 1984Feb 18, 1982—

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