WELL · 42-417-38317 · DISTRICT 7

Ivy-Oman #1

Y

Shackelford County · Lilly (Palo Pinto Lo.) field · Producing  · Vertical

Ivy-Oman #1 (API 42-417-38317) is a well in Shackelford County operated by Scott Operating Inc., completed October 1, 2001 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 22, 2001, permitted to 3,600 ft.

It was permitted by Glahn Resources, Inc. and has since transferred to Scott Operating Inc. on the wellbore schedule.

Completion filings report one formation top, including Palo Pinto.

Its lease has reported 11K barrels of oil since October 2001, last reporting in July 2026.

Operator of record

Scott Operating Inc.

Permitted by Glahn Resources, Inc.; the EWA schedule now lists a different operator.

Albany, TX · P-5 Y, filed Oct 4, 2025 · 30 permits on file · (325) 338-9717

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleScott Operating Inc.
Production reportsScott Operating, Inc.through Mar 2026
Latest permitGlahn Resources, Inc.Feb 22, 2001

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

3,600
total depth, ft
1
permits on file
Feb 22, 2001
last permit issued
Oct 1, 2001
completed
11K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 1, 2001
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
Ivy-Oman O-8-29070Lilly (Palo Pinto, Lo.)Scott Operating, Inc.111K0Oct 2001 – Jul 2026

Oil, barrels lease total

Last 12 months 9 · prior 12 26(-65%)

0102030202420252026

Chain of custody

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

  1. 1Glahn Resources, Inc.Oct 2001 → Dec 2009
  2. 2Scott Operating, Inc.Jan 2010 → Mar 2026
  3. 3Mudslinger Oil, L.L.C.Jun 2010 → Dec 2010
  4. 4Iron Horse Oil & Gas, Inc.Jan 2011 → May 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
505445-99DrillGlahn Resources, Inc.Feb 16, 2001Feb 22, 2001Apr 2, 20013,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-29070————

Formation tops

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

FormationMD ftSubsea
Palo PintoLOWER PALO PINTO3,433-1,822

Perforations

Perforated and open-hole intervals.

FromToType
3,4343,440Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251011180 S
4.53,5457.875155 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
00Dec 27, 2001Dec 4, 2001Yes
00Dec 14, 2001——

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