WELL · 42-423-32345 · DISTRICT 6

Ida #1

Y

Smith County · Chapel Hill (Travis Peak) field · Producing  · Vertical

Ida #1 (API 42-423-32345) is a well in Smith County operated by Atlas Operating LLC, completed July 4, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 13, 2014, permitted to 8,800 ft.

It was permitted by Brg Lone Star Ltd. and has since transferred to Atlas Operating LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Woodbine, Paluxy, Rodessa, Pettit.

Its lease has reported 12.7K barrels of oil and 58.4K mcf of gas since June 2014, last reporting in July 2026.

Operator of record

Atlas Operating LLC

Permitted by BRG Lone Star Ltd.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 4, 2025 · 78 permits on file · (281) 893-9400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAtlas Operating LLC
Production reportsAtlas Operating LLCthrough Mar 2026
Latest permitBRG Lone Star Ltd.Feb 13, 2014

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

8,800
total depth, ft
1
permits on file
Feb 13, 2014
last permit issued
Jul 4, 2014
completed
12.7K
cumulative oil, bbl
58.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 4, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Ida O-6-15388Chapel Hill (Travis Peak)Atlas Operating LLC112.7K58.4KJun 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 535 · prior 12 627(-15%)

050100202420252026

Chain of custody

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

  1. 1BRG Lone Star Ltd.Jul 2014 → Feb 2026
  2. 2Atlas Operating LLCMar 2026 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
777674-99DrillBRG Lone Star Ltd.Jan 20, 2014Feb 13, 2014Mar 23, 20148,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-15388————

Formation tops

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

FormationMD ftSubsea
Woodbine3,940-3,535
Paluxy5,540-5,135
Rodessa7,420-7,015
PettitPETTET8,080-7,675
Travis Peak8,277-7,872
Cotton Valley——
Nacatoch——

Perforations

Perforated and open-hole intervals.

FromToType
8,1068,214Perforated
8,2778,490Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,38511390 S
4.58,6507.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
00Apr 16, 2015Aug 14, 2014Yes

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