Mining Anthracite On Pitching And Flat Seams Over Mined-Out Areas

The American Institute of Mining, Metallurgical, and Petroleum Engineers

W. H. Moore E. T. Powell

Organization:: The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:: 13
File Size:: 540 KB
Publication Date:: Jan 1, 1941

Abstract

Email to a Friend

IN the early days of mining in the Anthracite field, only the thicker and better seams of coal were mined, because of the limited mining and coal-cleaning facilities, therefore many of the thinner and less productive seams were permitted to remain unmined. With improvements in mining methods, the introduction of modem preparation plants, and the increased market demand for small-size coal, the thinner and more laminated seams have now become assets. In many instances these seams overlie the mined-out beds of the thicker and better seams, from which all recoverable coal was removed by the conventional breast-and-pillar method of mining. Some collieries in certain sections of the Anthracite field are now relying on these thinner and laminated seams. For the purpose of illustration, a large area in the Hickory Swamp-Ridge Basin of the western middle coal field has been selected, where as early as 1898 the No. 4, or Little Buck Mountain, seam was mined and pillars removed. The No. 5, or Buck Mountain, seam lying on a comparatively light pitch and with intervening strata of but 55 ft. of rock was not mined until 1935. Farther east, in the same basin the Nos. 8 and 9 seams, which are two splits of the Mammoth seam, have been mined and robbed and the workings have been abandoned since 1896. The overlying No. 9 ¾ seam, or the upper split of the Mammoth, and the No. 9 ¾ or 4-ft. seam remained virgin, with only an interval of 50 ft. of rock separating them, and with 40 to 50 ft. of rock strata separating the No. 9 ½ seam from the completely mined area of the Nos. 8 and 9 seams. These seams lie on a pitch of 45° on the south side of the basin and on 75° on the north side of the basin. Mining has been carried on in the 9 ½ and 9 ¾ seams for 3 years on both dips of the basin, for a distance of 3500 ft. In some sections the overlying strata of the thicker seams previously mined have settled without any apparent breaks in the upper strata, as indications have shown in the top split of the Mammoth; while in other areas the roof and bottom of this top split of the Mammoth have settled unevenly, thereby causing the bottom and roof to break into blocks. In attempting to mine over a large area of the No. 5 or Buck Mountain seam, a similar settlement has been encountered; the roof of the seam has been broken and a considerable amount of timbering has been necessary in order to make the mining of the seam possible. The conventional breast-and-pillar method, using shaker conveyors, has been used in the No. 5 seam, and a slant-breast method in the mining of Nos. 9 ½ and 9 ¾ seams. MINING OF LIGHT-PITCH SEAMS The No. 4 seam was mined and robbed by the conventional breast-and-pillar system. In this area the seam pitched from 5° to 25° on the north dip, averaged 8 ft. in thickness and had a slate bottom and a

Citation

APA: W. H. Moore E. T. Powell (1941) Mining Anthracite On Pitching And Flat Seams Over Mined-Out Areas

MLA: W. H. Moore E. T. Powell Mining Anthracite On Pitching And Flat Seams Over Mined-Out Areas. The American Institute of Mining, Metallurgical, and Petroleum Engineers, 1941.

Export

CSV

RIS

Purchase this Article for $25.00

Create a Guest account to purchase this file
- or -
Log in to your existing Guest account

Unexpected error retrieving advertisement for PageView: Home_Index, Key: SidebarTop Name : Microsoft.Data.SqlClient.SqlException Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.) Stack : at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen() --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.InitializeReaderAsync(AsyncEnumerator enumerator, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at OneMine.Advertisements.Data.Queries.AdvertisementQueries.GetActiveAdvertisementByNameKeyAsync[T](Guid siteId, String pageViewName, String placementKey, CancellationToken cancellationToken) in D:\a\1\s\Lib\Data\Advertisements\Data\Queries\AdvertisementQueries.cs:line 39 at OneMine.Web.ViewComponents.ZoneTagViewComponent.InvokeAsync(String pageViewName, String placementKey) in D:\a\1\s\Web\ViewComponents\ZoneTagViewComponent.cs:line 84 -- Inner Exception -- Name : System.ComponentModel.Win32Exception Message: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Stack :