WELL · 42-213-30854 · DISTRICT 5

Scott J. O. #1

Y

Henderson County · Opelika (Travis Peak) field · Producing  · Vertical

Scott J. O. #1 (API 42-213-30854) is a well in Henderson County operated by Buffco Production Inc., completed May 22, 2003 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 16, 2002, permitted to 10,200 ft.

It was permitted by Phillips Energy, Inc. and has since transferred to Buffco Production Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including BMA, James Lime, Pettit, Travis Peak.

No lease production has been reported under this well’s leases.

Operator of record

Buffco Production Inc.

Permitted by Phillips Energy, Inc.; the EWA schedule now lists a different operator.

Longview, TX · P-5 Y, filed Sep 4, 2025 · 397 permits on file · (903) 736-4697

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBuffco Production Inc.
Production reportsBuffco Production Inc.through Apr 2026
Latest permitPhillips Energy, Inc.Oct 16, 2002

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

10,200
total depth, ft
1
permits on file
Oct 16, 2002
last permit issued
May 22, 2003
completed
0
cumulative oil, bbl
919K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 22, 2003
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Scott, J. O. G-5-196099Opelika (Travis Peak)Buffco Production Inc.10919KMay 2003 – Jul 2026

Gas, mcf lease total

Last 12 months 385 · prior 12 0

050100202420252026

Chain of custody

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

  1. 1Phillips Energy, Inc.May 2003 → Nov 2018
  2. 2Stroud Petroleum, Inc.Dec 2018 → Jul 2021
  3. 3Buffco Production Inc.Oct 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
524325-99DrillPhillips Energy, Inc.Oct 4, 2002Oct 16, 2002Mar 15, 200310,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-196099————

Formation tops

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

FormationMD ftSubsea
BMA8,486-7,971
James Lime8,977-8,462
Pettit9,313-8,798
Travis Peak9,528-9,013

Perforations

Perforated and open-hole intervals.

FromToType
10,08810,196Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,48011430 S
4.510,2007.875540 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
00Sep 5, 2003Jun 19, 2003Yes
00Aug 27, 2003——

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