WELL · 42-151-33341 · DISTRICT 7
Merlin 124 #1
Fisher County · Camp Springs SE. (Stawn) field · Vertical
Merlin 124 #1 (API 42-151-33341) is a plugged well in Fisher County, plugged January 26, 2024, last operated by Clear Fork Incorporated.
The RRC has issued one drilling permit, issued November 9, 2023, permitted to 7,000 ft.
It was permitted by Clear Fork, Incorporated and has since transferred to Clear Fork Incorporated on the wellbore schedule.
Operator of record
Clear Fork Incorporated
Permitted by Clear Fork, Incorporated; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Clear Fork, IncorporatedNov 9, 2023 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,000
- total depth, ft
- 1
- permits on file
- Nov 9, 2023
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Jan 26, 2024
Surface location
32.860469, -100.448461
Permit surface location from the RRC GIS record, in Fisher County.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 895132-99 | Drill | Clear Fork, Incorporated | Nov 7, 2023 | Nov 9, 2023 | Jan 2, 2024 | 7,000 |
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-151-33341 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-151-33341 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbors can.
Calico Jack 11142-151-33258
2.6 KM · Clear Fork, Incorporated · Section with this well →
| Coleman Junction | 2,900 | -960 |
| Noodle Creek - Disposal | 3,535 | -1,595 |
| Saddle Creek | 3,800 | -1,860 |
| Flippen - Disposal | 3,910 | -1,970 |
| Cisco | 4,090 | -2,150 |
| Crystal Falls - Disposal | 4,950 | -3,010 |
| Breckenridge - Disposal | — | |
| Dothan Sand - Disposal | — |
10 TOPS · FIRST 8
Iceman 46-4742-151-33278
4.1 KM · Browning Oil Company, Inc. · Section with this well →
| Coleman Junction | 2,980 | -1,026 |
| Noodle Creek - Disposal | 3,645 | -1,691 |
| Saddle Creek | 3,920 | -1,966 |
| Flippen - Disposal | 4,015 | -2,061 |
| Cisco | 4,110 | -2,156 |
| Crystal Falls - Disposal | 5,065 | -3,111 |
| Strawn | 6,490 | -4,536 |
| San Andres | — |
10 TOPS · FIRST 8
Maverick E 110-12742-151-33280
4.5 KM · Browning Oil Company, Inc. · Section with this well →
| Coleman Junction | 3,000 | -1,025 |
| Noodle Creek - Disposal | 3,630 | -1,655 |
| Saddle Creek | 3,900 | -1,925 |
| Flippen - Disposal | 4,000 | -2,025 |
| Cisco | 4,140 | -2,165 |
| Crystal Falls - Disposal | 5,080 | -3,105 |
| Hope - Disposal | — | |
| Breckenridge - Disposal | — |
10 TOPS · FIRST 8
WR Baker42-151-32973
4.7 KM · Ica Energy Operating, L.L.C. · Section with this well →
| Wichita-Albany | 1,830 | 85 |
| Coleman Junction | 2,530 | -615 |
| Coleman Junction | 2,770 | -855 |
| Dotham Lime | 3,296 | -1,381 |
| Canyon | 5,210 | -3,295 |
| Cline | 5,420 | -3,505 |
| Palo Pinto | 5,760 | -3,845 |
| Strawn | 5,791 | -3,876 |
17 TOPS · FIRST 8
Grunden GC42-151-32969
5.2 KM · Gunn Oil Company · Section with this well →
| Top of Noodlecreek | 3,415 | -1,465 |
| Noodle Creek | 3,415 | -1,465 |
| Black Shale | 5,581 | -3,631 |
| Base of Black Shale | 5,581 | -3,631 |
| Palo Pinto | 5,638 | -3,688 |
| Palo Pinto | 5,638 | -3,688 |
| Saddle Creek | — | |
| San Andres | — |
13 TOPS · FIRST 8
Blackbeard42-151-33244
5.3 KM · Clear Fork, Incorporated · Section with this well →
| Coleman Junction | 3,030 | -1,041 |
| Noodle Creek - Disposal | 3,675 | -1,686 |
| Saddle Creek | 3,940 | -1,951 |
| Flippen - Disposal | 4,035 | -2,046 |
| Cisco | 4,125 | -2,136 |
| Crystal Falls - Disposal | 5,085 | -3,096 |
| San Andres | — | |
| Hope - Disposal | — |
10 TOPS · FIRST 8
Grand Teton E 109-12842-151-33307
6.0 KM · Browning Oil Company, Inc. · Section with this well →
| Coleman Junction | 3,050 | -1,028 |
| Noodle Creek - Disposal | 3,710 | -1,688 |
| Saddle Creek | 3,975 | -1,953 |
| Flippen - Disposal | 4,080 | -2,058 |
| Crystal Falls - Disposal | 5,220 | -3,198 |
| San Andres | — | |
| Breckenridge - Disposal | — | |
| Cisco | — |
10 TOPS · FIRST 8
Palmer42-151-33082
6.3 KM · Sojourner Drilling Corporation · Section with this well →
| Coleman Junction | 2,540 | -616 |
| Noodle Creek - Disposal | 3,350 | -1,426 |
| Saddle Creek | 3,580 | -1,656 |
| Flippen - Disposal | 3,615 | -1,691 |
| Hope - Disposal | 3,720 | -1,796 |
| Breckenridge - Disposal | 3,765 | -1,841 |
| San Andres | — | |
| Dothan Sand - Disposal | — |
10 TOPS · FIRST 8
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/15133341, documented in the API reference.