TEXAS · WELLS · TERRY COUNTY · SUNTURA (LOWER CLEAR FORK) UNIT LEASE · API 42-445-32204 · DISTRICT 7B
Suntura (Lower Clear Fork) Unit #18W
Terry County · Suntura (Lower Clear Fork) field · Injection · Vertical
Suntura (Lower Clear Fork) Unit #18W (API 42-445-32204) is a well in Terry County operated by Basin Oil & Gas Operating LLC, completed August 18, 2008 and listed as injection on the RRC schedule.
The RRC has issued one drilling permit, issued July 2, 2008, permitted to 8,350 ft.
It was permitted by Great Western Drilling Company and has since transferred to Basin Oil & Gas Operating LLC on the wellbore schedule.
Its lease has reported 5.33M barrels of oil and 511K mcf of gas since October 2007, last reporting volume in April 2026. The lease carries 45 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit, with 46.7K barrels injected in the 12 months reported through November 2025.
Operator of record
Permitted by Great Western Drilling Company; the EWA schedule now lists a different operator.
- Based in
- Fort Worth, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- May 21, 2026
- Permits on file
- 152
- Phone
- (817) 820-8910
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Basin Oil & Gas Operating LLC |
| Production reports | Basin Oil & Gas Operating, LLCthrough Apr 2026 |
| Latest permit | Great Western Drilling CompanyJul 2, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,350
- total depth, ft
- 1
- permits on file
- Jul 2, 2008
- last permit issued
- Aug 18, 2008
- completed
- 5.33M
- cumulative oil, bbl
- 511K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2007 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 18, 2008
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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; they carry 45 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Suntura (Lower Clear Fork) Unit O-11-69175 | Suntura (Lower Clear Fork) | Basin Oil & Gas Operating, LLC | 45 | 5.33M | 511K | Oct 2007 – Apr 2026 |
Oil, barrels lease total
Last 12 months 170,675 · prior 12 147,053(+16%)
Gas, mcf lease total
Last 12 months 13,998 · prior 12 9,319(+50%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Great Western Drilling CompanyOct 2007 → Oct 2024
- 2Basin Oil & Gas Operating, LLCNov 2024 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 659919-99 | Drill | Great Western Drilling Company | Apr 17, 2008 | Jul 2, 2008 | Jul 14, 2008 | 8,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 18, 2008 | Suntura (Lower Clear Fork) Unit O-11-69175 | Suntura (Lower Clear Fork) | Basin Oil & Gas Operating LLC | Injection | 8,350 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,648 | 7,976 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,473 | 12.25 | 1,200 S |
| 5.5 | 8,350 | 7.875 | 700 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | May 19, 2009 | Sep 5, 2008 | Yes |
| 00 | Mar 24, 2009 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Aug 17, 2011. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITY | TIFF | 4,500 to 8,341 | Aug 17, 2011run Jul 26, 2008 | 3.21 |
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.
- Wellbore filings for 42-445-32204 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-445-32204 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 46.7K
- bbl, last 12 reported months
- 1.14M
- bbl, all reported
- Nov 2025
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000098013 | H-1 Injection | Active | 200 | 2,750 | 7,400–8,400 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 46,727 · prior 12 51,676(-10%)
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/44532204, documented in the API reference.