WELL · 42-413-32791 · DISTRICT 7

Thornburg 27 #1

Y

Schleicher County · Caraway & Smith (1800 Sd.) field · Producing  · Vertical

Thornburg 27 #1 (API 42-413-32791) is a well in Schleicher County operated by Oil Projects LLC, completed April 16, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 9, 2011, permitted to 5,000 ft.

It was permitted by Hannathon Petroleum, LLC and has since transferred to Oil Projects LLC on the wellbore schedule.

Completion filings report 3 formation tops, including 1800' Sand, Harkey Sand, Strawn.

Its lease has reported 14.5K barrels of oil and 8.92K mcf of gas since March 2012, last reporting in July 2026.

Operator of record

Oil Projects LLC

Permitted by Hannathon Petroleum, LLC; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jul 4, 2026 · 17 permits on file · (714) 624-8157

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOil Projects LLC
Production reportsOil Projects, LLCthrough Apr 2026
Latest permitHannathon Petroleum, LLCNov 9, 2011

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

5,000
total depth, ft
1
permits on file
Nov 9, 2011
last permit issued
Apr 16, 2012
completed
14.5K
cumulative oil, bbl
8.92K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 16, 2012
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
Thornburg 27 O-9-17903Caraway & Smith (1800 Sd.)Oil Projects, LLC114.5K8.92KMar 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 216 · prior 12 0

050100150202420252026

Chain of custody

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

  1. 1Hannathon Petroleum, LLCMar 2012 → Feb 2023
  2. 2Oil Projects, LLCNov 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
727738-99DrillHannathon Petroleum, LLCNov 7, 2011Nov 9, 2011Dec 1, 20115,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-17903————

Formation tops

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

FormationMD ftSubsea
1800' Sand1,735541
Harkey Sand3,952-1,676
StrawnSTRAWN LIME4,385-2,109

Perforations

Perforated and open-hole intervals.

FromToType
1,7301,735Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62555211340 S
5.54,8787.875665 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
00May 31, 2013May 31, 2012Yes

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) and the University Lands library. 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/41332791, documented in the API reference.