WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-337-81470

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-337-81470Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

18 LOG FILES ON 16 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Robeson #2SW42-337-33815Montague, TX · Salty S Disposal Wells LP0.68NEUTRON/DENSITY POROSITYTIFF792 to 4,999Sep 2, 2009run Aug 23, 2006
Robeson #2SW42-337-33815Montague, TX · Salty S Disposal Wells LP0.68SURVEYS CASED HOLETIFF792 to 4,998Sep 2, 2009run Aug 23, 2006
Blackmon B Unit #2HHZ42-337-35220Montague, TX · Scout Energy Management LLC0.80RESISTIVITYTIFF4,970 to 12,600Nov 11, 2016run Nov 23, 2013
Blackmon a Unit #2HHZ42-337-35213Montague, TX · Scout Energy Management LLC0.89RESISTIVITYTIFF4,960 to 13,320Nov 11, 2016run Oct 30, 2013
Gray Unit #1HHZ42-337-35215Montague, TX · Scout Energy Management LLC0.95RESISTIVITYTIFF1,033 to 11,144Nov 11, 2016run Nov 1, 2013
Fat Dog C Unit #1HHZ42-337-35388Montague, TX · Scout Energy Management LLC1.21OtherTIFF951 to 10,837Jul 16, 2020
Fat Dog C Unit #1HHZ42-337-35388Montague, TX · Scout Energy Management LLC1.21RESISTIVITYTIFF951 to 10,837Nov 13, 2017run Nov 8, 2014
Gray Unit #2HHZ42-337-35216Montague, TX · Scout Energy Management LLC1.24RESISTIVITYTIFF1,002 to 12,690Nov 11, 2016run Nov 13, 2013
Hankins Unit #1HHZ42-337-35145Montague, TX · Eagleridge Operating LLC1.27RESISTIVITYTIFF5,000 to 10,660Aug 29, 2016run Jul 28, 2013
Boedeker D Unit #1HHZ42-337-35147Montague, TX · Eagleridge Operating LLC1.29RESISTIVITYTIFF4,250 to 6,812Sep 9, 2016run Oct 15, 2013
McCarty Unit #2HHZ42-337-35196Montague, TX · Scout Energy Management LLC1.36RESISTIVITYTIFF5,080 to 13,091Oct 7, 2016run Oct 9, 2013
Fat Dog C Unit #2HHZ42-337-35386Montague, TX · Scout Energy Management LLC1.41RESISTIVITYTIFF986 to 11,815Nov 13, 2017run Oct 31, 2014
McCarty Unit #1HHZ42-337-35195Montague, TX · Scout Energy Management LLC1.47RESISTIVITYTIFF4,850 to 10,855Oct 7, 2016run Oct 18, 2013
Pullen #1HHZ42-337-35364Montague, TX · Scout Energy Management LLC1.48RESISTIVITYTIFF985 to 9,520Jun 12, 2017run Jun 21, 2014
Gray Unit #3HHZ42-337-35217Montague, TX · Scout Energy Management LLC1.53RESISTIVITYTIFF1,000 to 13,560Nov 11, 2016run Nov 24, 2013
Fat Dog a Unit #2HHZ42-337-35392Montague, TX · Scout Energy Management LLC1.65RESISTIVITYTIFF0 to 6,925Oct 16, 2017run Dec 2, 2014
Clearfork Unit #1HHZ42-337-35363Montague, TX · Scout Energy Management LLC1.80RESISTIVITYTIFF990 to 11,050Jun 12, 2017run Jun 14, 2014
Fat Dog a Unit #1HHZ42-337-35391Montague, TX · Scout Energy Management LLC1.82RESISTIVITYTIFF4,800 to 6,805Oct 16, 2017run Dec 1, 2014

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. 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. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.